Re: ambulkdelete - Mailing list pgsql-general

From Jim C. Nasby
Subject Re: ambulkdelete
Date
Msg-id 20060327125126.GD80726@pervasive.com
Whole thread Raw
In response to ambulkdelete  (David Hoksza <david.hoksza@seznam.cz>)
Responses Re: ambulkdelete  (David Hoksza <david.hoksza@seznam.cz>)
List 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@phonebook.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@phonebook.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@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

pgsql-general by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: pg 8.1.2 performance issue
Next
From: "Qingqing Zhou"
Date:
Subject: Re: PANIC: heap_update_redo: no block