|
Home > Archive > PostgreSQL Discussion > March 2006 > ambulkdelete
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| David Hoksza 2006-03-26, 1:25 pm |
| Hi, I would like to know, when ambulkdelete is run. I thought that
when tuple is deleted so bulkdelete is run, but when I set breakpoint
to btbulkdelete, it doesn't stop there. Does it mean, that
ambulkdelete is run just when I use VACUUM?
David Hoksza
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
| |
| Jim C. Nasby 2006-03-27, 7:37 am |
| On Sun, Mar 26, 2006 at 08:30:44PM +0200, David Hoksza wrote:
> Hi, I would like to know, when ambulkdelete is run. I thought that
> when tuple is deleted so bulkdelete is run, but when I set breakpoint
> to btbulkdelete, it doesn't stop there. Does it mean, that
> ambulkdelete is run just when I use VACUUM?
BTW, -hackers is a better place for this...
decibel@phonebook.1[6:50]~/pgsql/HEAD/src/backend:5%grep -ri ambulkdelete *
access/index/indexam.c: GET_REL_PROCEDURE(am
bulkdelete);
commands/vacuum.c: * ambulkdelete call, because (a) the scan happens within the index AM for
commands/vacuumlazy.c: * ambulkdelete call, because (a) the scan happens within the index AM for
decibel@phonebook.1[6:50]~/pgsql/HEAD/src/backend:6%grep -ri btbulkdelete *
access/nbtree/nbtree. c:btbulkdelete(PG_FU
NCTION_ARGS)
access/nbtree/nbtree.c: * concurrent btbulkdelete scan cannot pass our position --- if it
access/nbtree/README:(see btbulkdelete).
decibel@phonebook.1[6:50]~/pgsql/HEAD/src/backend:7%
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
| |
| Simon Riggs 2006-03-28, 3:27 am |
| On Sun, 2006-03-26 at 20:30 +0200, David Hoksza wrote:
> Hi, I would like to know, when ambulkdelete is run. I thought that
> when tuple is deleted so bulkdelete is run, but when I set breakpoint
> to btbulkdelete, it doesn't stop there.
> Does it mean, that
> ambulkdelete is run just when I use VACUUM?
Yes
Best Regards, Simon Riggs
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
| |
| David Hoksza 2006-03-28, 7:28 am |
| OK, thx...
____________________
____________
27. bøezna 2006, 14:51:26, napsal jste:
JCN> On Sun, Mar 26, 2006 at 08:30:44PM +0200, David Hoksza wrote:[color=darkred
]
JCN> BTW, -hackers is a better place for this...
JCN> decibel@phonebook.1[6:50]~/pgsql/HEAD/src/backend:5%grep -ri ambulkdelete *
JCN> access/index/indexam.c: GET_REL_PROCEDURE(am
bulkdelete);
JCN> commands/vacuum.c: * ambulkdelete call, because (a) the
JCN> scan happens within the index AM for
JCN> commands/vacuumlazy.c: * ambulkdelete call, because (a) the
JCN> scan happens within the index AM for
JCN> decibel@phonebook.1[6:50]~/pgsql/HEAD/src/backend:6%grep -ri btbulkdelete *
JCN> access/nbtree/nbtree. c:btbulkdelete(PG_FU
NCTION_ARGS)
JCN> access/nbtree/nbtree.c: * concurrent btbulkdelete scan
JCN> cannot pass our position --- if it
JCN> access/nbtree/README:(see btbulkdelete).
JCN> decibel@phonebook.1[6:50]~/pgsql/HEAD/src/backend:7%
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
|
|
|
|
|