From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
Cc: | Kevin Grittner <kgrittn(at)ymail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)2ndquadrant(dot)com>, "Hilbert, Sebastian" <Sebastian(dot)Hilbert(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [GENERAL] pg_upgrade ?deficiency |
Date: | 2013-12-02 16:41:10 |
Message-ID: | 20131202164110.GC5274@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Sun, Dec 1, 2013 at 09:22:52AM +0100, Karsten Hilbert wrote:
> 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.
The use-case would be that default_transaction_read_only is turned on in
postgresql.conf as part of installing the old and/or new cluster. The
9.4 PGOPTIONS fix for pg_upgrade _will_ allow such a cluster to be
upgraded.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
From | Date | Subject | |
---|---|---|---|
Next Message | Zev Benjamin | 2013-12-02 16:44:52 | Re: unnest on multi-dimensional arrays |
Previous Message | Jeff Janes | 2013-12-02 16:14:59 | Re: While only running pg_dump, postgresql performs writes inside base/ directory. How can we stop this? |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2013-12-02 16:52:43 | Re: DATE type output does not follow datestyle parameter |
Previous Message | Alvaro Herrera | 2013-12-02 16:25:08 | Re: In-core regression tests for replication, cascading, archiving, PITR, etc. |