On Mon, Dec 2, 2013 at 06:57:53PM +0100, Karsten Hilbert wrote:
> On Mon, Dec 02, 2013 at 11:41:10AM -0500, Bruce Momjian wrote:
>
> > > > 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.
> >
> > The use-case would be that default_transaction_read_only is turned on in
> > postgresql.conf
>
> Are you telling me which use case I initially asked
> about on this thread ?
No, this is another use-case that is fixed the pg_upgrade patch. The
ALTER DATABASE SET is also fixed by this patch.
-- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ Everyone has their own god. +