From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | David Hoksza <david(dot)hoksza(at)seznam(dot)cz> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: ambulkdelete |
Date: | 2006-03-27 12:51:26 |
Message-ID: | 20060327125126.GD80726@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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(at)phonebook(dot)1[6:50]~/pgsql/HEAD/src/backend:5%grep -ri ambulkdelete *
access/index/indexam.c: GET_REL_PROCEDURE(ambulkdelete);
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(at)phonebook(dot)1[6:50]~/pgsql/HEAD/src/backend:6%grep -ri btbulkdelete *
access/nbtree/nbtree.c:btbulkdelete(PG_FUNCTION_ARGS)
access/nbtree/nbtree.c: * concurrent btbulkdelete scan cannot pass our position --- if it
access/nbtree/README:(see btbulkdelete).
decibel(at)phonebook(dot)1[6:50]~/pgsql/HEAD/src/backend:7%
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Qingqing Zhou | 2006-03-27 12:52:11 | Re: PANIC: heap_update_redo: no block |
Previous Message | Jim C. Nasby | 2006-03-27 12:49:20 | Re: pg 8.1.2 performance issue |