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: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Fixing GIN for empty/null/full-scan cases
Date: 2011-01-13 00:46:31
Message-ID: 5DB905A3-EADB-467B-BAFB-3CFB7B4A8019@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jan 12, 2011, at 4:35 PM, Tom Lane wrote:

>> Did a signature change or something?
>
> Yeah. I think if you just load up the current contrib/intarray first,
> you'll be fine (ignore all the object-already-exists errors).

Oh, from 9.1devel? yeah, okay. Will do that tomorrow (finishing the current load to make sure that there are no other errors I can't ignore, but won't see among all the intarray stuff tomorrow).

>> Is there something that needs a compatibility interface of some kind?
>
> No, what we need is a decent extension package manager ;-)

Yeah. Maybe you can do that this weekend? Or, I dunno, while you “sleep” tonight?

Best,

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-01-13 00:47:12 Re: Bug in pg_describe_object, patch v2
Previous Message Tom Lane 2011-01-13 00:44:12 Re: Add function dependencies