| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Vik Fearing <vik(dot)fearing(at)dalibo(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: SQL access to database attributes |
| Date: | 2014-06-21 20:21:32 |
| Message-ID: | CAFj8pRBaeZOacKbmcBsi2dwr+T3yXBvjxXF+oP1WqWWA6bAfGg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Second question related to second patch:
Must be new syntax ALLOW_CONNECTIONS? Should not be (ENABLE | DISABLE)
CONNECTION ? This doesn't need any new keyword.
Regards
Pavel
2014-06-21 22:11 GMT+02:00 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>:
> Hello
>
> I am looking createdb_alterdb_grammar_refactoring.v1.patch
>
> http://www.postgresql.org/message-id/53868E57.3030908@dalibo.com
>
> Is any reason or is acceptable incompatible change CONNECTION_LIMIT
> instead CONNECTION LIMIT? Is decreasing parser size about 1% good enough
> for breaking compatibility?
>
> Surely this patch cannot be backported what is proposed there.
>
> Regards
>
> Pavel
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Fearing | 2014-06-21 21:14:02 | Re: SQL access to database attributes |
| Previous Message | Pavel Stehule | 2014-06-21 20:11:17 | SQL access to database attributes |