| From: | Vik Fearing <vik(dot)fearing(at)dalibo(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | 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:39:50 |
| Message-ID: | 53A85856.2000707@dalibo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
> See, e.g., what we do for COPY.
Exactly. We're still carrying around baggage from 7.2!
Backward compatibility: yes.
Backward documentation: no.
--
Vik
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-06-23 16:40:00 | Re: releaseOk and LWLockWaitForVar |
| Previous Message | Andres Freund | 2014-06-23 16:38:17 | Re: Atomics hardware support table & supported architectures |