Re: SQL access to database attributes

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:18:33
Message-ID: 53A5F6A9.2080300@dalibo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 06/21/2014 10:21 PM, Pavel Stehule wrote:
> Second question related to second patch:
>
> Must be new syntax ALLOW_CONNECTIONS?

It doesn't *have* to be called that, but that's what the corresponding
column in pg_database is called so why add confusion? (Actually, it's
called datallowconn but that would be a silly name on the SQL level.)

> Should not be (ENABLE | DISABLE) CONNECTION ?

I don't think it should be, no.

> This doesn't need any new keyword.

None of this requires any new keywords. That's the whole point of the
refactoring patch.
--
Vik

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Vik Fearing 2014-06-21 21:54:58 Re: idle_in_transaction_timeout
Previous Message Vik Fearing 2014-06-21 21:14:02 Re: SQL access to database attributes