From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Florian Pflug <fgp(at)phlo(dot)org>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: LOCK for non-tables |
Date: | 2011-01-15 15:25:49 |
Message-ID: | 27670.1295105149@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Sat, Jan 15, 2011 at 6:29 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> I think we should have a section in the release notes on Deprecated
>> Features, noting that certain things will be removed later and should be
>> changed now and not relied upon in the future. A pending
>> incompatibilities list.
> Agreed. Of course, the problem is sometimes we don't do what we say
> we're going to do, but it's worth a try.
I think if we had a formal list of planned removals, it'd be more likely
that they'd actually happen. Right now there's no process at all
driving such things forward.
I suggest also marking each item with a release in which we intend to do
it, so we don't have to try to remember whether a reasonable amount of
time has elapsed.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-01-15 15:30:04 | Re: Streaming base backups |
Previous Message | Noah Misch | 2011-01-15 15:25:48 | Re: ALTER TYPE 0: Introduction; test cases |