Re: pg_upgrade defaulting to port 25432

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Robert Haas <robertmhaas(at)gmail(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 02:33:06
Message-ID: 1309141727-sup-9387@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Darren Duncan 2011-06-27 05:29:06 Re: Range Types, constructors, and the type system
Previous Message Robert Haas 2011-06-27 02:31:47 Re: Re: starting to review the Extend NOT NULL representation to pg_constraint patch