Search Postgresql Archives

Re: Locking Down a Database

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Le 15/07/2010 16:21, Shoaib Mir a écrit :
> On Thu, Jul 15, 2010 at 10:53 PM, Terry Lee Tucker
> <terry@xxxxxxxxxxxxxxx <mailto:terry@xxxxxxxxxxxxxxx>> wrote:
> 
>     Greetings:
> 
>     I occasionally find the need to perform some maintenance on one or
>     more of
>     thirteen different databases. Typically, due to the interaction
>     between the
>     databases, I need to lock down the databases for a short period of
>     time so
>     that no updates are being performed anywhere. 
> 
> 
> There is something that I saw the other day in PG 9.0 i.e.
> transaction_read_only which might be helpful in your case. 

transaction_read_only is not something you can set. It's set by the
server, to "on" on a hotstandby server, and else to "off". And
default_transaction_read_only can be "unset", so not that useful too.

-- 
Guillaume
 http://www.postgresql.fr
 http://dalibo.com

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux