Re: pg_upgrade and PGPORT

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade and PGPORT
Date: 2011-05-12 05:22:36
Message-ID: 1305177756.10392.2.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On ons, 2011-05-11 at 18:36 -0400, Bruce Momjian wrote:
> Robert Haas wrote:
> > 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.
>
> OK, the attached patch does this, but allows PGCLIENTENCODING to be
> passed in. The new output looks like:
>
> Performing Consistency Checks
> -----------------------------
> ignoring libpq environment variable PGPORT

I haven't tried it, but I suppose option.c will now make use of PGPORT
and then later you get that message that it was ignored?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2011-05-12 06:43:55 Re: Infinity bsearch crash on Windows
Previous Message Robert Haas 2011-05-12 03:53:55 Re: Extension Packaging