Re: SQL access to database attributes - Mailing list pgsql-hackers

From Vik Fearing
Subject Re: SQL access to database attributes
Date
Msg-id 53AC563D.5040509@dalibo.com
Whole thread Raw
In response to Re: SQL access to database attributes  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: SQL access to database attributes  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 06/23/2014 06:45 PM, Pavel Stehule wrote:
>
>
>
> 2014-06-23 18:39 GMT+02:00 Vik Fearing <vik.fearing@dalibo.com
> <mailto:vik.fearing@dalibo.com>>:
>
>     On 06/23/2014 06:21 PM, Robert Haas wrote:
>     > On Sun, Jun 22, 2014 at 2:59 PM, Pavel Stehule
>     <pavel.stehule@gmail.com <mailto:pavel.stehule@gmail.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?
>
>
> It is fair to our users. It can be deprecated, ok, we can write in doc -
> this feature will be deprecated in next three years. Don't use it, but
> this should be documentated.

Okay, here is version two of the refactoring patch that documents that
the with-space version is deprecated but still accepted.

The feature patch is not affected by this and so I am not attaching a
new version of that.
--
Vik

Attachment

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: pgaudit - an auditing extension for PostgreSQL
Next
From: Tom Lane
Date:
Subject: Re: Changes in amcanreturn() interface to support multicolumn indexes