Re: Locking Down a Database

Поиск
Список
Период
Сортировка
От Guillaume Lelarge
Тема Re: Locking Down a Database
Дата
Msg-id 4C3F1E4A.30603@lelarge.info
обсуждение исходный текст
Ответ на Re: Locking Down a Database  (Shoaib Mir <shoaibmir@gmail.com>)
Список pgsql-general
Le 15/07/2010 16:21, Shoaib Mir a écrit :
> On Thu, Jul 15, 2010 at 10:53 PM, Terry Lee Tucker
> <terry@chosen-ones.org <mailto:terry@chosen-ones.org>> 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

В списке pgsql-general по дате отправления:

Предыдущее
От: Artur Dabrowski
Дата:
Сообщение: Re: Incorrect FTS results with GIN index
Следующее
От: Anthony Presley
Дата:
Сообщение: Re: Idle In Transaction