Re: [GENERAL] pg_upgrade ?deficiency - Mailing list pgsql-hackers

From Karsten Hilbert
Subject Re: [GENERAL] pg_upgrade ?deficiency
Date
Msg-id 20131202175752.GD4373@hermes.hilbert.loc
Whole thread Raw
In response to Re: [GENERAL] pg_upgrade ?deficiency  (Bruce Momjian <bruce@momjian.us>)
Responses Re: [GENERAL] pg_upgrade ?deficiency
List pgsql-hackers
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 ?

Karsten
-- 
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block
Next
From: Andres Freund
Date:
Subject: Re: Draft release notes for 9.3.2