On 2013-11-22 12:45:25 -0800, Kevin Grittner wrote: > Tom Lane <t...@sss.pgh.pa.us> wrote: > > > That looks sane for pg_dump, but I would rather have expected > > that pg_dumpall would need to emit the same thing (possibly more > > than once due to reconnections). > > I was kinda surprised myself. I changed it for pg_dump, tested > that, and then tested pg_dumpall to get a baseline, and the setting > was taken care of.
pg_dumpall is lazy and just executes pg_dump for every database, that's the reason... But are you sure it also unsets default_transaction_readonly for the roles etc. it creates? Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
