Re: [HACKERS] GIN code managing entry insertion not able to differentiate fresh and old indexes

2015-03-21 Thread Michael Paquier
On Sat, Mar 21, 2015 at 7:27 AM, Bruce Momjian wrote: > On Thu, Nov 20, 2014 at 05:22:02PM +0900, Michael Paquier wrote: >> While playing with the GIN code for an upcoming patch, I noticed that >> when inserting a new entry in a new index, this code path is not able >> to make the difference if the

Re: [HACKERS] GIN code managing entry insertion not able to differentiate fresh and old indexes

2015-03-20 Thread Bruce Momjian
On Thu, Nov 20, 2014 at 05:22:02PM +0900, Michael Paquier wrote: > Hi all, > > While playing with the GIN code for an upcoming patch, I noticed that > when inserting a new entry in a new index, this code path is not able > to make the difference if the index is in a build state or not. > Basically

[HACKERS] GIN code managing entry insertion not able to differentiate fresh and old indexes

2014-11-20 Thread Michael Paquier
Hi all, While playing with the GIN code for an upcoming patch, I noticed that when inserting a new entry in a new index, this code path is not able to make the difference if the index is in a build state or not. Basically, when entering in ginEntryInsert@gininsert.c GinBtree built via ginPrepareEn