Tom Lane wrote: > Bruce Momjian <br...@momjian.us> writes: > > pg_upgrade is not about to start reading through postgresql.conf looking > > for a definition for data_directory --- there are too many cases where > > this could go wrong. It would need a full postgresql.conf parser. > > 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. We've had requests for that > type of functionality before, IIRC. The --describe-config option does > something related, but not what's needed here.
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. We could minimize that by using this feature only if postgresql.conf exists in the specified data directory but PG_VERSION does not. Adding this features is similar to this TODO item: Allow configuration files to be independently validated This still seems like a lot to backpatch. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers