Re: ambulkdelete - Mailing list pgsql-general

From David Hoksza
Subject Re: ambulkdelete
Date
Msg-id 965758211.20060328141620@seznam.cz
Whole thread Raw
In response to Re: ambulkdelete  ("Jim C. Nasby" <jnasby@pervasive.com>)
List pgsql-general
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:
>> 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?

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(ambulkdelete);
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_FUNCTION_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%


pgsql-general by date:

Previous
From: "surabhi.ahuja"
Date:
Subject: 32 bit applications against 64 bit postgres server
Next
From: "David Welton"
Date:
Subject: Concurrency question