Re: pg_upgrade defaulting to port 25432 - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: pg_upgrade defaulting to port 25432
Date
Msg-id 1308957579.9571.0.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: pg_upgrade defaulting to port 25432  (Bruce Momjian <bruce@momjian.us>)
Responses Re: pg_upgrade defaulting to port 25432
List pgsql-hackers
On fre, 2011-06-24 at 16:34 -0400, Bruce Momjian wrote:
> > > It also creates two new environment variables,
> > > OLDPGPORT and NEWPGPORT, to control the port values because we
> don't
> > > want to default to PGPORT anymore.
> > 
> > I would prefer that all PostgreSQL-related environment variables
> start
> > with "PG".
> 
> OK, attached.  I was also using environment variables for PGDATA and
> PGBIN do I renamed those too to begin with 'PG'.

I'm wondering why pg_upgrade needs environment variables at all.  It's a
one-shot operation.  Environment variables are typically used to shared
default settings across programs.  I don't see how that applies here.



pgsql-hackers by date:

Previous
From: David Christensen
Date:
Subject: Re: Deriving release notes from git commit messages
Next
From: Noah Misch
Date:
Subject: Re: Another issue with invalid XML values