Re: [PATCHES] GIN improvements - Mailing list pgsql-hackers

From Teodor Sigaev
Subject Re: [PATCHES] GIN improvements
Date
Msg-id 488734A5.9030503@sigaev.ru
Whole thread Raw
In response to Re: [PATCHES] GIN improvements  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCHES] GIN improvements  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [PATCHES] GIN improvements  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> once, for regular VACUUM I think you really have to call it within
> each bulkdelete operation.  

Exactly what I did in last patch.

> There's probably no point in optimizing
> it away in VACUUM FULL either, since surely it'll be fast to call
> index_cleanup when there's nothing in the pending list?

Sure, with empty pending list insertcleanup will just lock/unlock metapage.

> Yeah, I was going to complain about that next :-).  Autovacuum isn't
> going to trigger as a result of INSERT operations; somehow we have
> to teach it what to do for GIN indexes.  I remember we discussed this
> at PGCon but I don't think we decided exactly what to do...
So, may be we just move insertcleanup call to   ginbulkdelete/ginvacuumcleanup 
but leave aminsertcleanup field in pg_proc for a future.

> I've already made a number of changes to the patch; let me keep working
> on it and send it back to you later.
ok

-- 
Teodor Sigaev                                   E-mail: teodor@sigaev.ru
  WWW: http://www.sigaev.ru/
 


pgsql-hackers by date:

Previous
From: Oleg Bartunov
Date:
Subject: Re: [GENERAL] Fragments in tsearch2 headline
Next
From: Tatsuo Ishii
Date:
Subject: WITH RECUSIVE patches 0723