From: | Terry Lee Tucker <terry(at)chosen-ones(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Locking Down a Database |
Date: | 2010-07-15 12:53:57 |
Message-ID: | 201007150853.57108.terry@chosen-ones.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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. I do not want to shut down the
postmasters as it is a clustered environment and would rather just leave that
alone. Also, since this is a 24 hour shop, it would be good if people could
still query, but not change any data. All this work is done at times like
03:00 in the morning and the number of people working at that time is limited
to five or six. Is there some easy way of doing this without having people log
out of the application?
TIA...
--
Terry Lee Tucker
tel: (336) 372-5432; cell: (336) 404-6897
terry(at)chosen-ones(dot)org
From | Date | Subject | |
---|---|---|---|
Next Message | Artur Dabrowski | 2010-07-15 13:09:30 | Incorrect FTS result with GIN index |
Previous Message | Richard Huxton | 2010-07-15 11:59:11 | Re: error "CDT FATAL: invalid frontend message type 69" |