Re: Fixing GIN for empty/null/full-scan cases

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Abe Ingersoll <abe(at)abe(dot)us>
Subject: Re: Fixing GIN for empty/null/full-scan cases
Date: 2011-01-18 23:45:15
Message-ID: E8A0DA70-9327-46A7-82B4-91E187659234@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jan 18, 2011, at 3:08 PM, Tom Lane wrote:

>> Shall I send you data with the other two columns?:
>
> No, I see no reason to think that has much to do with it. I'm wondering
> if your table is itself a bit bloated ...

Nope. Just ran the bloat query from check_postgres.pl. Bloat is 0. Not surprising since the table was created by inserting from another table (the original with the gist indexes) and has not been updated since.

Any other ideas?

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-01-18 23:46:48 Re: Fixing GIN for empty/null/full-scan cases
Previous Message Bruce Momjian 2011-01-18 23:36:31 Re: test_fsync label adjustments