Re: pg_dump/pg_restore vs default_transaction_read_only under PG 13.2

From: Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: pg_dump/pg_restore vs default_transaction_read_only under PG 13.2
Date: 2021-06-20 19:58:52
Message-ID: YM+d/MtdrQEnO+Wd@hermes.hilbert.loc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2021-06-20 20:14:06 Re: pg_dump/pg_restore vs default_transaction_read_only under PG 13.2
Previous Message Karsten Hilbert 2021-06-20 19:34:45 Re: pg_dump/pg_restore vs default_transaction_read_only under PG 13.2