pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Josh Berkus <josh@agliodbs.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: postgres hackers <pgsql-hackers@postgresql.org>
Cc: Oleg Bartunov <oleg@sai.msu.su>
Subject: Re: GIN vs. Partial Indexes
Date: Sat, 23 Oct 2010 12:01:21 -0700
Message-ID: <4CC33101.1000205@agliodbs.com> (raw)
In-Reply-To: <AANLkTi=kQK3UFrQ5G82uMpdyy0bnS9KWSKAaovvyJNaZ@mail.gmail.com>
References: <4CAE6A92.4060703@agliodbs.com>
	<11352.1286506328@sss.pgh.pa.us>
	<AANLkTi=tYR5z+DJkTk3Ffom9vmMN95QajyOmGFQraMVb@mail.gmail.com>
	<13837.1286560056@sss.pgh.pa.us>
	<AANLkTi=kQK3UFrQ5G82uMpdyy0bnS9KWSKAaovvyJNaZ@mail.gmail.com>

On 10/08/2010 02:44 PM, Robert Haas wrote:
>>  In any case, I would expect that GIN could actually do this quite
>>  efficiently.  What we'd probably want is a concept of a "null word",
>>  with empty indexable rows entered in the index as if they contained the
>>  null word.  So there'd be just one index entry with a posting list of
>>  however many such rows there are.

So, given the lack of objections to this idea, do we have a plan for 
fixing GIN?

-- 
                                   -- Josh Berkus
                                      PostgreSQL Experts Inc.
                                      http://www.pgexperts.com

view thread (12+ messages)  latest in thread

Message-ID: <4CC33101.1000205@agliodbs.com>
Permalink:  ../4CC33101.1000205@agliodbs.com/
Also on:    postgresql.org/message-id/4CC33101.1000205@agliodbs.com

copy link · copy postgr.es

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: josh@agliodbs.com, robertmhaas@gmail.com, tgl@sss.pgh.pa.us, oleg@sai.msu.su
  Subject: Re: GIN vs. Partial Indexes
  In-Reply-To: <4CC33101.1000205@agliodbs.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox