Re: pg_upgrade defaulting to port 25432

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christopher Browne <cbbrowne(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade defaulting to port 25432
Date: 2011-06-27 16:03:09
Message-ID: BANLkTimPGhr0xh5hRCbZN9VCkxbSvvBKxg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Jun 26, 2011 at 10:33 PM, Alvaro Herrera
<alvherre(at)commandprompt(dot)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(at)momjian(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christian Ullrich 2011-06-27 16:26:25 Re: Small 9.1 documentation fix (SSPI auth)
Previous Message Robert Haas 2011-06-27 15:59:56 Re: Word-smithing doc changes