Re: pg_upgrade and PGPORT

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade and PGPORT
Date: 2011-05-11 18:33:57
Message-ID: BANLkTi=OMNf_SUEVzt3+LuQyv17bfwZcNQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 11, 2011 at 2:18 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Or you could just "unsetenv" instead of complaining.

+1 for that.

> I would like to think that eventually pg_upgrade won't start a
> postmaster at all, but connect using something more like a standalone
> backend.  So someday the issue might go away --- but that someday
> isn't especially close.

And +1 for that, too.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2011-05-11 18:48:18 Re: Standbys which don't synch to disk?
Previous Message Peter Eisentraut 2011-05-11 18:29:48 Tables cannot have INSTEAD OF triggers