Am Sun, Jun 20, 2021 at 01:47:47PM -0400 schrieb Tom Lane: > Hence, the only way to make this scenario work would be for the > restore script to explicitly override default_transaction_read_only. [...] > Also, doing so would result in ignoring default_transaction_read_only > no matter what the source of that was. I think it's probably not > hard to construct scenarios where someone would really not be happy > about such behavior.
Any chance pg_dump (and/or pg_restore) might gain an option --ignore-read-only ? That way, PostgreSQL need not decide for users. Thanks, Karsten -- GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B
