From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Vik Fearing <vik(dot)fearing(at)dalibo(dot)com> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: SQL access to database attributes |
Date: | 2014-06-23 16:48:23 |
Message-ID: | CA+TgmoZOB06CVJ9Q80C7WnkT3LLv=3AS5UCjCcHoKFU1XMBjPA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jun 23, 2014 at 12:39 PM, Vik Fearing <vik(dot)fearing(at)dalibo(dot)com> wrote:
> On 06/23/2014 06:21 PM, Robert Haas wrote:
>> On Sun, Jun 22, 2014 at 2:59 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>>> I found only one problem - first patch introduce a new property
>>> CONNECTION_LIMIT and replace previously used "CONNECTION LIMIT" in
>>> documentation. But "CONNECTION LIMIT" is still supported, but it is not
>>> documented. So for some readers it can look like breaking compatibility, but
>>> it is false. This should be documented better.
>>
>> Yeah, I think the old syntax should be documented also.
>
> Why do we want to document syntax that should eventually be deprecated?
Because otherwise existing users will wonder if their dumps can still
be restored on newer systems.
And also, because documentation is, in general, a good thing.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-06-23 16:49:24 | Re: /proc/self/oom_adj is deprecated in newer Linux kernels |
Previous Message | Robert Haas | 2014-06-23 16:46:11 | Re: Atomics hardware support table & supported architectures |