From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Avoiding Application Re-test |
Date: | 2008-08-07 15:21:47 |
Message-ID: | 6421.1218122507@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> Simon Riggs wrote:
>> What I would like is a parameter called sql_compatibility which has
>> settings such as 8.3, 8.4 etc.. By default it would have the value 8.4,
>> but for people that want to upgrade *without* retesting their
>> application, they could set it to 8.3.
> Won't there normally be a number of changes that *cannot* be covered by
> such a parameter, without a whole lot more work in the patch?
Yeah. It's not always possible, and certainly not always easy, to
provide such a behavior. Moreover, an "all or nothing" switch doesn't
seem like it'd be such a big win: presumably, the reason you are updating
to 8.4 is you would like something you can't get in 8.3. So you're
going to have to turn the switch off sooner rather than later, making
the value questionable.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2008-08-07 15:28:20 | Re: Infrastructure changes for recovery |
Previous Message | Alvaro Herrera | 2008-08-07 15:17:10 | Re: patch: Add columns via CREATE OR REPLACE VIEW |