[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [HACKERS] [GENERAL] pg_upgrade ?deficiency
From:       Tom Lane <tgl () sss ! pgh ! pa ! us>
Date:       2013-11-30 23:48:02
Message-ID: 884.1385855282 () sss ! pgh ! pa ! us
[Download RAW message or body]

Kevin Grittner <kgrittn@ymail.com> writes:
> Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> What is the point of this, given that Kevin fixed pg_dumpall? 
>> Don't those fixes take care of the issue?

> 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.

Oh, I had forgotten that pg_upgrade will run additional commands
against the new cluster after restoring the dumpall output.
I guess we do need something like what Bruce did to cover that.

			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
[prev in list] [next in list] [prev in thread] [next in thread]