| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Dave Page <dpage(at)pgadmin(dot)org> |
| Subject: | Re: Dropping PL language retains support functions |
| Date: | 2012-03-06 21:15:57 |
| Message-ID: | CA+Tgmoa-4iScxKnAjEWxiFef7bwF6yWnoTnwiW9CJW6aaqvuXQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 6, 2012 at 3:28 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On mån, 2012-03-05 at 19:37 -0500, Bruce Momjian wrote:
>> The exact case is that the user was using plpython2u in PG 9.0, but
>> the PG 9.1 one-click installer only supplies plpython3u.
>
> That seems like a pretty stupid choice to me, if it's true.
>
> That doesn't address your issue, but users shouldn't be forced to drop
> their languages during an upgrade in the first place.
Hmm. I had been thinking that it is only possible to support one or
the other, thus the need for a compatibility break at some point would
be forced, but reading the documentation, it seems that it we can ship
both as long as nobody tries to use both at the same time. I wonder
why we didn't do that.
Dave?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thom Brown | 2012-03-06 21:18:58 | Re: Command Triggers, patch v11 |
| Previous Message | Robert Haas | 2012-03-06 21:10:16 | Re: foreign key locks, 2nd attempt |