| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Vik Fearing <vik(dot)fearing(at)dalibo(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:21:35 |
| Message-ID: | CA+TgmoZa_V8Nyt6K3+W8CR_anVGpp8QrzAPdLbd4vJFKqJn4Zw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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. See, e.g.,
what we do for COPY.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | MauMau | 2014-06-23 16:22:26 | Re: Use a signal to trigger a memory context dump? |
| Previous Message | Robert Haas | 2014-06-23 16:20:29 | Re: replication identifier format |