Re: [PATCHES] GIN improvements

From: Teodor Sigaev <teodor(at)sigaev(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] GIN improvements
Date: 2008-07-22 17:22:32
Message-ID: 48861758.4070507@sigaev.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

> I started to look at this. I don't understand why VACUUM does an insert
> cleanup before starting to vacuum, but VACUUM FULL doesn't?

Hmm. May be I missed something, but I don't understand where and what... I tried
to track all places of ambultdelete call. aminsertcleanup should be called
before any ambulkdelete, because ambulkdelete doesn't scan pending list which
can store items to be deleted and hence index will store item pointers to absent
tuples.

> needed is the one at vacuum startup, which tempts me to propose that
> the new AM entry point should be called "amvacuumstartup", instead of
> wiring in the assumption that what it's for is specifically cleanup
> of insertions.

That's possible but inserts into index should be forbidden between
amvacuumstartup and last call of ambulkdelete.

>
> Comments? I can make the change if you think it's okay --- I'm busy
> cleaning up docs and comments at the moment.

--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2008-07-22 17:23:50 Re: Plans for 8.4
Previous Message chris 2008-07-22 17:16:04 Slony-I playing with system catalog

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2008-07-22 17:50:10 Re: [PATCHES] GIN improvements
Previous Message Tom Lane 2008-07-22 16:03:25 Re: [PATCHES] GIN improvements