Re: pg_upgrade default ports in the --help output

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Виктор Егоров <vyegorov(at)gmail(dot)com>
Cc: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: pg_upgrade default ports in the --help output
Date: 2012-10-04 21:06:56
Message-ID: 20121004210656.GA11729@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Oct 4, 2012 at 04:50:09PM +0300, Виктор Егоров wrote:
> 2012/10/4 Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>:
> > http://www.postgresql.org/docs/9.2/static/pgupgrade.html
> > "Obviously, no one should be accessing the clusters during the upgrade.
> > pg_upgrade defaults to running servers on port 50432 to avoid unintended
> > client connections. You can use the same port number for both clusters when
> > doing an upgrade because the old and new clusters will not be running at the
> > same time. However, when checking an old running server, the old and new
> > port numbers must be different."
>
> Should have checked the docs first, sorry for the noise.
>
> >> Why is this different from:
> >> --with-pgport=PORTNUM set default port number [5432]
> >
> > Where is this coming from?
>
> ./configure --help

Ah, OK. The configure output to configure the default port number used
by the server and libpq clients. These are compile-time flags, while
the pg_upgrade flags are run-time, meaning when you run the binary, not
when you compile it.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2012-10-04 23:14:31 Re: Thousands of schemas and ANALYZE goes out of memory
Previous Message Thalis Kalfigkopoulos 2012-10-04 20:44:54 Trajectory of a [Pg] DBA