Re: LOCK DATABASE
От | Robert Haas |
---|---|
Тема | Re: LOCK DATABASE |
Дата | |
Msg-id | BANLkTi=hmTe_ufJ_ZEq4uG6WknQJ9qzmPA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: LOCK DATABASE ("Ross J. Reedstrom" <reedstrm@rice.edu>) |
Ответы |
Re: LOCK DATABASE
|
Список | pgsql-hackers |
On Thu, May 26, 2011 at 12:28 PM, Ross J. Reedstrom <reedstrm@rice.edu> wrote: > Perhaps the approach to restricting connections should not be a database > object lock, but rather an admin function that does the equivalent of > flipping datallowconn in pg_database? To me, that seems like a better approach, although it's a little hard to see how we'd address Alvaro's desire to have it roll back automatically when the session disconnected. The disconnect might be caused by a FATAL error, for example. I'm actually all in favor of doing more things via SQL rather than configuration files. The idea of some ALTER SYSTEM command seems very compelling to me. I just don't really like this particular implementation, which to me seems far too bound up in implementation details I'd rather not rely on. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: