Re: pg_upgrade using appname to lock out other users - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pg_upgrade using appname to lock out other users
Date
Msg-id 201106161348.p5GDmCt29837@momjian.us
Whole thread Raw
In response to Re: pg_upgrade using appname to lock out other users  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_upgrade using appname to lock out other users
Re: pg_upgrade using appname to lock out other users
List pgsql-hackers
Tom Lane wrote:
> "Ross J. Reedstrom" <reedstrm@rice.edu> writes:
> > As an operations guy, the idea of an upgrade using a random,
> > non-repeatable port selection gives me the hebejeebees.
> 
> Yeah, I agree.  The latest version of the patch doesn't appear to have
> any random component to it, though --- it just expects the user to
> provide port numbers as switches.

Oh, you wanted pg_upgrade to pick a random port number?  I can do that,
but how would it check to see it is unused?

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Leonardo Francalanci
Date:
Subject: Re: use less space in xl_xact_commit patch
Next
From: Robert Creager
Date:
Subject: Re: Why polecat and colugos are failing to build back branches