Re: How to shorten a chain of logically replicated servers - Mailing list pgsql-general

From Laurenz Albe
Subject Re: How to shorten a chain of logically replicated servers
Date
Msg-id de3fe6630101932c1e7796017ca2f0c63d70f4e6.camel@cybertec.at
Whole thread Raw
In response to Re: How to shorten a chain of logically replicated servers  (Mike Lissner <mlissner@michaeljaylissner.com>)
Responses Re: How to shorten a chain of logically replicated servers
List pgsql-general
On Tue, 2020-01-07 at 23:17 -0800, Mike Lissner wrote:
> > You'd have to suspend all data modification on A in that interval.
> 
> I know how to stop the DB completely, but I can't think of any obvious
> ways to make sure that it doesn't get any data modification for a
> period of time. Is there a trick here? This is feeling a bit hopeless.

The simplest solution would be to stop the applications that use PostgreSQL.

You could block client connections using a "pg_hba.conf" entry
(and kill the established connections).

Another option can be to set "default_transaction_read_only = on",
but that will only work if the clients don't override it explicitly.

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com




pgsql-general by date:

Previous
From: Niels Jespersen
Date:
Subject: SV: Writing Postgres Extensions in C on Windows
Next
From: github kran
Date:
Subject: Re: Upgrade PostgreSQL 9.6 to 10.6