| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | David Christensen <david(at)endpoint(dot)com> |
| Cc: | Christopher Browne <cbbrowne(at)gmail(dot)com>, Jaime Casanova <jaime(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: LOCK DATABASE |
| Date: | 2011-05-19 05:34:11 |
| Message-ID: | 1305781803-sup-7833@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from David Christensen's message of jue may 19 00:55:36 -0400 2011:
> How would this differ from just UPDATE pg_database SET datallowconn = FALSE for the databases in question?
Several ways actually. First, it is automatically gone when the locking
session disconnects (so it clean ups after itself). Second, it doesn't
require manually updating the catalogs, which is frowned upon (with good
reason). Third, the database owner could do it, not just superuser.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2011-05-19 05:38:17 | Re: LOCK DATABASE |
| Previous Message | David Christensen | 2011-05-19 04:55:36 | Re: LOCK DATABASE |