From: | Markus Wanner <markus(at)bluegap(dot)ch> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: A deprecation policy |
Date: | 2009-02-11 08:21:43 |
Message-ID: | 49928A97.5030400@bluegap.ch |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
Peter Eisentraut wrote:
> I have been thinking, with a semi-formal deprecation policy, we could
> make these decisions with more confidence.
+1 (I'm reading this as a very general proposal also targeting C APIs,
not only GUCs).
> Comments?
With the proposed policy we'd have to recommend users to upgrade in
steps of at least every 2nd release for these obsoleteness and
deprecation warnings to have any effect. However, I'm often seeing users
taking pretty large steps like upgrading from 7.4 to 8.3.
OTOH those users are certainly prepared for major incompatibilities and
prepared to adjust their code. However, the value of 2 in N+2 is
certainly debatable.
Regards
Markus Wanner
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2009-02-11 08:48:49 | Re: 64 bit PostgreSQL 8.3.6 build on AIX 5300-09-02-0849 with IBM XL C/C++ 10.1.0.1 - initdb fails (could not dump unrecognized node type: 650) |
Previous Message | Heikki Linnakangas | 2009-02-11 08:13:30 | Re: A deprecation policy |