From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(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 using appname to lock out other users |
Date: | 2011-06-16 01:29:18 |
Message-ID: | 201106160129.p5G1TIW18979@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Stephen Frost wrote:
-- Start of PGP signed section.
> Bruce,
>
> * Bruce Momjian (bruce(at)momjian(dot)us) wrote:
> > I have researched this and need feedback.
>
> In general, I like the whole idea of using random/special ports for the
> duration of the upgrade. I agree that we need to keep the ability to
> check the existing clusters. My gut feeling is this: keep the existing
> port options just as they are, so --check works just fine, etc. Use
> *only* long-options for the "ports to use during the actual upgrade" and
> discourage their use- we want people to let a random couple of ports be
> used during the upgrade to minimize the risk of someone connecting to
> one of the systems. Obvioulsy, there may be special cases where that's
> not an option, but I don't think we need to make it easy nor do I think
> we need to have a short option for it.
Having long options mean different than short options seems very
confusing.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2011-06-16 01:33:02 | Re: pg_upgrade using appname to lock out other users |
Previous Message | Christopher Browne | 2011-06-16 01:20:38 | Re: Commitfest 2011-6 is underway! Reviewers needed. |