From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | 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-24 20:34:33 |
Message-ID: | 201106242034.p5OKYXT17154@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut wrote:
> On tor, 2011-06-23 at 21:39 -0400, Bruce Momjian wrote:
> > I have created the following patch which uses 25432 as the default port
> > number for pg_upgrade.
>
> I don't think we should just steal a port from the reserved range.
> Picking a random port from the private/dynamic range seems more
> appropriate.
Oh, I didn't know about that. I will use 50432 instead.
> > 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'.
Patch attached.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
Attachment | Content-Type | Size |
---|---|---|
/rtmp/pg_upgrade | text/x-diff | 10.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-06-24 20:52:45 | Re: Deriving release notes from git commit messages |
Previous Message | Simon Riggs | 2011-06-24 20:27:22 | Re: ALTER TABLE lock strength reduction patch is unsafe |