From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Steve Crawford <scrawford(at)pinpointresearch(dot)com>, "Mr(dot) Aaron W(dot) Swenson" <titanofold(at)gentoo(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_upgrade - add config directory setting |
Date: | 2011-09-29 23:27:35 |
Message-ID: | 201109292327.p8TNRZm03255@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Tom Lane wrote:
> >> Yeah. I think the only sensible way to do this would be to provide an
> >> operating mode for the postgres executable that would just parse the
> >> config file and spit out requested values.
>
> > That would certainly solve the problem, though it would have to be
> > backpatched all the way back to 8.4, and it would require pg_upgrade
> > users to be on newer minor versions of Postgres.
>
> I would just say "no" to people who expect this to work against older
> versions of Postgres. I think it's sufficient if we get this into HEAD
> so that it will work in the future.
Well, it is going to work in the future only when the _old_ version is
9.2+. Specifically, pg_upgrade using the flag could be patched to just
9.2, but the flag has to be supported on old and new backends for that
to work.
--
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 | Alexander | 2011-09-30 00:54:22 | Re: REVIEW proposal: a validator for configuration files |
Previous Message | Michael Paquier | 2011-09-29 23:27:08 | Re: pg_regress input/output directory option |