Re: Restoring a database problem

From: "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Restoring a database problem
Date: 2020-10-03 11:30:50
Message-ID: 20201003113050.GC18543@hjp.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2020-09-30 20:11:12 -0500, Ron wrote:
> 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.
[...]
> > I would modify pg_hba.conf to block access temporarily.
>
> As would I; it's the first thing I thought of...

Interesting. The first thing I thought of was "iptables"[1]. Probably shows
that I'm a Linux guy first and a database guy second.

hp

[1] Yes, I know that this doesn't affect connections through Unix
sockets.

--
_ | Peter J. Holzer | Story must make more sense than reality.
|_|_) | |
| | | hjp(at)hjp(dot)at | -- Charles Stross, "Creative writing
__/ | http://www.hjp.at/ | challenge!"

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Glen Eustace 2020-10-03 19:35:12 Re: Restoring a database problem
Previous Message Peter J. Holzer 2020-10-03 09:04:10 Re: pg_upgrade Python version issue on openSUSE