Re: citext operator precedence fix - Mailing list pgsql-hackers

From Robert Haas
Subject Re: citext operator precedence fix
Date
Msg-id CA+TgmoZrOR-ZtZsGg55wOaHsz1e=idu0SVYyXVWOESAfysDwyw@mail.gmail.com
Whole thread Raw
In response to Re: citext operator precedence fix  ("David E. Wheeler" <david@kineticode.com>)
Responses Re: citext operator precedence fix
Re: citext operator precedence fix
List pgsql-hackers
On Thu, Sep 22, 2011 at 2:16 PM, David E. Wheeler <david@kineticode.com> wrote:
> On Sep 22, 2011, at 11:14 AM, Kevin Grittner wrote:
>
>>> No, because if 1.1 was installed on 8.4, you'd need the commands
>>> to move all its functions into the extension, not re-create them.
>>
>> Shouldn't a version installed on 8.4 be installed as "unpackaged"?
>> Doesn't citext--unpackaged--1.0.sql contain the commands to move all
>> its functions into the extension?
>
> It contains everything need to move 1.0 functions into the extension. If Josh adds new functions they obviously would
notbe moved. So a new script would need to move them. And unpackaged--1.1 does not first run unpackaged--1.0.
 

I believe the point David is trying to make is that someone might take
an 9.2 version of a contrib module and manually install it on an 8.4
server by executing the install script, perhaps with some amount of
hackery.

But I don't think we're required to support that case.  If the user
does a non-standard install, it's their job to deal with the fallout.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: citext operator precedence fix
Next
From: "David E. Wheeler"
Date:
Subject: Re: citext operator precedence fix