On Sat, Nov 30, 2013 at 03:21:08PM -0800, Kevin Grittner wrote: > > If your argument is that you want pg_upgrade to work even if the > > user already turned on default_transaction_read_only in the *new* > > cluster, I would humbly disagree with that goal, for pretty much > > the same reasons I didn't want pg_dump overriding it. > > If there were databases or users with default_transaction_read_only > set in the old cluster, the pg_dumpall run will cause that property > to be set in the new cluster, so what you are saying seems to be > that a cluster can't be upgraded to a new major release if any > database within it has that set.
That is *precisely* my use case which I initially asked about. Karsten -- GPG key ID E4071346 @ gpg-keyserver.de E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
