pg_upgrade and PGPORT

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: pg_upgrade and PGPORT
Date: 2011-05-11 17:36:38
Message-ID: 1305135398.8811.2.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

pg_upgrade is a bit schizophrenic concerning the PGPORT environment
variable. On the one hand, there is this code in option.c that wants to
make use of it:

old_cluster.port = getenv("PGPORT") ? atoi(getenv("PGPORT")) : DEF_PGPORT;
new_cluster.port = getenv("PGPORT") ? atoi(getenv("PGPORT")) : DEF_PGPORT;

On the other hand, check.c will reject a set PGPORT because it's a libpq
environment variable. Should we make an exception for PGPORT, like we
did for PGCLIENTENCODING?

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2011-05-11 17:40:08 Re: hint bit cache v5
Previous Message Josh Berkus 2011-05-11 17:30:30 Re: Standbys which don't synch to disk?