Re: [GENERAL] pg_upgrade ?deficiency

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>, "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-11-23 00:25:57
Message-ID: 1385166357.84476.YahooMailNeo@web162902.mail.bf1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> On Fri, Nov 22, 2013 at 01:55:10PM -0800, Kevin Grittner wrote:
>
>> It does nothing about pg_upgrade, which is sort of a separate
>> issue.  My inclination is that connections to the new cluster
>> should set this and connections to the old should not.
>
> It is going to be tricky to conditionally set/reset an
> environment variable for default_transaction_read_only for
> old/new clusters.

Why?  If you know you have connected to the new cluster, set it to
off; if you know you have connected to the old cluster, don't touch
it.

> We never write to the old cluster, so I am not sure
> setting/resetting default_transaction_read_only is needed.

I'm sure it isn't.  That's why I said that connections to the old
cluster should not set it -- by which I meant they should not do
anything with it.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kevin Grittner 2013-11-23 00:38:53 Re: [GENERAL] pg_upgrade ?deficiency
Previous Message Ken Tanzer 2013-11-22 23:51:00 Re: Getting non_NULL right-side values on a non-matching join?

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2013-11-23 00:38:53 Re: [GENERAL] pg_upgrade ?deficiency
Previous Message Michael Paquier 2013-11-23 00:10:40 Re: Can we trust fsync?