| From: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
|---|---|
| To: | Vik Fearing <vik(dot)fearing(at)dalibo(dot)com> |
| Cc: | PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SQL access to database attributes |
| Date: | 2014-05-24 04:03:43 |
| Message-ID: | CAJKUy5heQmtGCODxUeQNwsBN60DJB53Nz88HAjjf88m9y_v8Sg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 23, 2014 at 10:53 PM, Vik Fearing <vik(dot)fearing(at)dalibo(dot)com> wrote:
>
> It was suggested to me that these options should either error out if
> there are existing connections or terminate said connections. I don't
> agree with that because there is no harm in connecting to a template
> database (how else do you modify it?), and adding a reject rule in
> pg_hba.conf doesn't disconnect existing users so why should turning off
> ALLOW CONNECTIONS do it?
>
Which lead us to the question: you need to connect to the database to
modify it, don't you? then, how do you change ALLOW CONNECTIONS to
true?
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
Phone: +593 4 5107566 Cell: +593 987171157
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Fearing | 2014-05-24 04:06:26 | Re: SQL access to database attributes |
| Previous Message | Vik Fearing | 2014-05-24 03:53:56 | SQL access to database attributes |