| From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Restoring a database problem |
| Date: | 2020-10-01 01:11:12 |
| Message-ID: | 82097994-6772-dfd7-84e0-8f150af25e26@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 9/30/20 7:11 PM, Bruce Momjian wrote:
> On Thu, Oct 1, 2020 at 01:00:21PM +1300, Glen Eustace wrote:
>> I have had to do this so rarely and it has almost always been in a bit of a
>> panic so may well be missing something really obvious.
>>
>> What I want to know is how to quiese a database to that I can restore it.
>>
>> I need to close all existing connections and the prevent people/processes from
>> connecting again until the restore has completed.
>>
>> Currently I have been logging into a bunch of servers and stopping various
>> daemons, then on the database server killing processes until the database is
>> apparently idle then dropping the database and doing the restore. Then
>> restarting the daemons etc. I am sure I am not doing this the right way so
>> advice gratefully received.
> I would modify pg_hba.conf to block access temporarily.
As would I; it's the first thing I thought of...
--
Angular momentum makes the world go 'round.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthias Apitz | 2020-10-01 06:36:55 | Re: Problem close curser after rollback |
| Previous Message | Rob Sargent | 2020-10-01 00:41:13 | Re: Restoring a database problem |