Re: pg_dump/pg_restore vs default_transaction_read_only under PG 13.2 - Mailing list pgsql-general

From Karsten Hilbert
Subject Re: pg_dump/pg_restore vs default_transaction_read_only under PG 13.2
Date
Msg-id YM+d/MtdrQEnO+Wd@hermes.hilbert.loc
Whole thread Raw
In response to Re: pg_dump/pg_restore vs default_transaction_read_only under PG 13.2  (Karsten Hilbert <Karsten.Hilbert@gmx.net>)
List pgsql-general
Am Sun, Jun 20, 2021 at 09:34:45PM +0200 schrieb Karsten Hilbert:

> Any chance pg_dump (and/or pg_restore) might gain an option
> --ignore-read-only ?   That way, PostgreSQL need not decide
> for users.

Or, options --pre-dump-sql and -post-dump-sql ?

Users could then run setup/teardown SQL for the dump
to end up the way they need it to.

Karsten
--
GPG  40BE 5B0E C98E 1713 AFA6  5BC0 3BEA AC80 7D4F C89B



pgsql-general by date:

Previous
From: Karsten Hilbert
Date:
Subject: Re: pg_dump/pg_restore vs default_transaction_read_only under PG 13.2
Next
From: Adrian Klaver
Date:
Subject: Re: pg_dump/pg_restore vs default_transaction_read_only under PG 13.2