Re: pg_restore with connection limit 0

From: Олег Самойлов <splarv(at)ya(dot)ru>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_restore with connection limit 0
Date: 2019-11-27 16:29:57
Message-ID: B29C01A8-E264-4F07-BE5E-9E5CEA178546@ya.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


> 27 нояб. 2019 г., в 18:14, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> написал(а):

> Why not use pg_hba.conf to allow only connection from superuser for duration?

We considered this, but we don't have direct access to the linux server, only sql connection. The application run in a kubernetes, etc.

The most simple approach to block concurrent access to the database, may be, is run all pg_restore inside single transaction. But this is impossible with --create option, but --create option is the only way to restore database settings. And this is impossible for us, because we need pg_restore in 3 stages.

It is inconvenient that the pg_restore has functionality for 3 stages, but don't has functionality to block database for time of this 3 stages.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Carter 2019-11-27 18:49:37 Install different directory issues
Previous Message Adrian Klaver 2019-11-27 15:14:42 Re: pg_restore with connection limit 0