Re: Fixing GIN for empty/null/full-scan cases - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: Fixing GIN for empty/null/full-scan cases
Date
Msg-id 5DB905A3-EADB-467B-BAFB-3CFB7B4A8019@kineticode.com
Whole thread Raw
In response to Re: Fixing GIN for empty/null/full-scan cases  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Fixing GIN for empty/null/full-scan cases
List 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
errorsI 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




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Add function dependencies
Next
From: Tom Lane
Date:
Subject: Re: Bug in pg_describe_object, patch v2