Re: [HACKERS] Re: [COMMITTERS] pgsql: Implement "fastupdate" support for GIN indexes, in which we try

2009-03-25 Thread Bruce Momjian
Tom Lane wrote: > Robert Haas writes: > > 2009/3/24 Tom Lane : > >> catversion bumped because of change in GIN's pg_am entry, and because > >> the format of GIN indexes changed on-disk (there's a metapage now, > >> and possibly a pending list). > > > Will this break pg_migrator? > > No worse tha

Re: [HACKERS] Re: [COMMITTERS] pgsql: Implement "fastupdate" support for GIN indexes, in which we try

2009-03-24 Thread Tom Lane
Robert Haas writes: > 2009/3/24 Tom Lane : >> catversion bumped because of change in GIN's pg_am entry, and because >> the format of GIN indexes changed on-disk (there's a metapage now, >> and possibly a pending list). > Will this break pg_migrator? No worse than it's already broken by hash inde

[HACKERS] Re: [COMMITTERS] pgsql: Implement "fastupdate" support for GIN indexes, in which we try

2009-03-24 Thread Robert Haas
2009/3/24 Tom Lane : > Implement "fastupdate" support for GIN indexes, in which we try to accumulate > multiple index entries in a holding area before adding them to the main index > structure.  This helps because bulk insert is (usually) significantly faster > than retail insert for GIN. > > This