Andres Freund <and...@2ndquadrant.com> writes: > On 2013-11-22 13:07:29 -0800, Kevin Grittner wrote: >> I'm not sure I understand. Could you give an example of what >> you're concerned about?
> pg_dumpall first spits out global data (users, databases, tablespaces) > and then invokes pg_dump for every single database. So I'd very strongly > suspect that your patch will issue the CREATE ROLE etc. calls without > unsetting default_transaction_readonly. Yeah, that's what I was wondering about. I don't think pg_dumpall -g invokes pg_dump at all, so how could that case work? Maybe it would only fail if the postgres database is read-only, though. Try it with default-read-only set in postgresql.conf instead of as a database property. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers