Re: GIN, partial matches, lossy bitmaps

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Teodor Sigaev <teodor(at)sigaev(dot)ru>, Robert Haas <robertmhaas(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: GIN, partial matches, lossy bitmaps
Date: 2009-03-23 15:38:05
Message-ID: 15127.1237822685@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> Attached is the remainder of the patch with relatively minor fixes.
> The main change I made is to get rid of the changes in gincostestimate;
> I agree with Robert that it's probably inappropriate to consider the
> current pending-list size during planning. I haven't really reviewed
> any of the rest of it; this is just to have a clean patch against HEAD.

Is that patch (fast_insert_gin-0.30.gz) still the latest version of
the fast-insert patch? Has anyone else done any further work?

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dimitri Fontaine 2009-03-23 17:44:14 Re: contrib function naming, and upgrade issues
Previous Message Tom Lane 2009-03-23 14:43:04 Re: contrib function naming, and upgrade issues