Re: Restoring a database problem - Mailing list pgsql-general

From Bruce Momjian
Subject Re: Restoring a database problem
Date
Msg-id 20201001001100.GC26860@momjian.us
Whole thread Raw
In response to Restoring a database problem  (Glen Eustace <geustace@godzone.net.nz>)
Responses Re: Restoring a database problem  (Rob Sargent <robjsargent@gmail.com>)
Re: Restoring a database problem  (Ron <ronljohnsonjr@gmail.com>)
List pgsql-general
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.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee




pgsql-general by date:

Previous
From: Glen Eustace
Date:
Subject: Restoring a database problem
Next
From: Rob Sargent
Date:
Subject: Re: Restoring a database problem