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

From Robert Haas
Subject Re: pg_upgrade defaulting to port 25432
Date
Msg-id BANLkTimPGhr0xh5hRCbZN9VCkxbSvvBKxg@mail.gmail.com
Whole thread Raw
In response to Re: pg_upgrade defaulting to port 25432  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: pg_upgrade defaulting to port 25432
List pgsql-hackers
On Sun, Jun 26, 2011 at 10:33 PM, Alvaro Herrera
<alvherre@commandprompt.com> wrote:
> Excerpts from Robert Haas's message of vie jun 24 22:22:55 -0400 2011:
>> On Fri, Jun 24, 2011 at 7:47 PM, Bruce Momjian <bruce@momjian.us> wrote:
>
>> > You want the environment variable support removed?
>>
>> I don't.  It's production usefulness is questionable, but it's quite
>> handy for testing IMO.
>
> If that's what you want, I think being able to read a file (whose
> filename you pass with a switch to pg_upgrade) with a bunch of settings
> is even more convenient.  Heck, maybe it's more convenient for the user
> too.

If someone wants to do the work, I'm all in favor.  But I don't feel
that we should insist that Bruce do it.

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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Word-smithing doc changes
Next
From: Jonathan Corbet
Date:
Subject: Re: Deriving release notes from git commit messages