On Fri, Nov 22, 2013 at 04:25:57PM -0800, Kevin Grittner wrote:
> Bruce Momjian <bruce@momjian.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.
Remember this is being done with a PGOPTIONS environment variable, so
you need to set/reset this on every action. I just don't see the value.
-- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ Everyone has their own god. +
