| From: | Vik Fearing <vik(dot)fearing(at)dalibo(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: SQL access to database attributes |
| Date: | 2014-06-21 21:14:02 |
| Message-ID: | 53A5F59A.30906@dalibo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Vik
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Fearing | 2014-06-21 21:18:33 | Re: SQL access to database attributes |
| Previous Message | Pavel Stehule | 2014-06-21 20:21:32 | Re: SQL access to database attributes |