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

From Pavel Stehule
Subject Re: SQL access to database attributes
Date
Msg-id CAFj8pRBundV6i0W5t8OYSgfuvz2V65FKxL1ZS4BW+RnxFh56sQ@mail.gmail.com
Whole thread Raw
In response to Re: SQL access to database attributes  (Vik Fearing <vik.fearing@dalibo.com>)
List pgsql-hackers



2014-06-21 23:14 GMT+02:00 Vik Fearing <vik.fearing@dalibo.com>:
On 06/21/2014 10:11 PM, Pavel Stehule wrote:
> Hello
>
> I am looking createdb_alterdb_grammar_refactoring.v1.patch
>
> http://www.postgresql.org/message-id/53868E57.3030908@dalibo.com

Thank you for looking at this.

> Is any reason or is acceptable incompatible change CONNECTION_LIMIT
> instead CONNECTION LIMIT? Is decreasing parser size about 1% good enough
> for breaking compatibility?

How is compatibility broken?  The grammar still accepts the old way, I
just changed the documentation to promote the new way.

> Surely this patch cannot be backported what is proposed there.

There are reasons I can think of not to backport this first patch, but
breaking compatibility isn't one of them.

I am sorry, tomorrow I have to read it again

Pavel
 
--
Vik

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: proposal: new long psql parameter --on-error-stop
Next
From: "Erik Rijkers"
Date:
Subject: Re: proposal: new long psql parameter --on-error-stop