Re: LOCK DATABASE - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: LOCK DATABASE
Date
Msg-id 1305781803-sup-7833@alvh.no-ip.org
Whole thread Raw
In response to Re: LOCK DATABASE  (David Christensen <david@endpoint.com>)
List 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@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: David Christensen
Date:
Subject: Re: LOCK DATABASE
Next
From: Andres Freund
Date:
Subject: Re: LOCK DATABASE