Re: Locking Down a Database

From: Shoaib Mir <shoaibmir(at)gmail(dot)com>
To: Terry Lee Tucker <terry(at)chosen-ones(dot)org>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Locking Down a Database
Date: 2010-07-15 14:21:45
Message-ID: AANLkTilkpGMLZGYvWA5EUvaLsctDWVyCX3cGeEAuKUTV@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Jul 15, 2010 at 10:53 PM, Terry Lee Tucker <terry(at)chosen-ones(dot)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.
--
Shoaib Mir
http://shoaibmir.wordpress.com/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Merlin Moncure 2010-07-15 14:21:52 Re: cache lookup failed for function 19119
Previous Message Artur Dabrowski 2010-07-15 13:29:51 Re: Incorrect FTS results with GIN index