From: | Patrik Novotny <panovotn(at)redhat(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | [PATCH] Move user options to the end of the command in pg_upgrade |
Date: | 2019-09-10 12:37:19 |
Message-ID: | CAE_EZkiThteQrYvctZUy2yq4SQPY-_CPrz9K=AaUPiA8TyTuZA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
when the environment variable POSTGRESQL_UPGRADE_PGUPGRADE_OPTIONS is
used to specify options for pg_upgrade, options related to
unix_socket_directory/ies are being overridden by hardcoded options,
making it difficult to upgrade in some usecases.
The attached patch changes the order of those options so that the
hardcoded ones are eventually overridden by the user specified
options.
As I can see that in PostgreSQL 12 this issue has been solved by
implementing the -socketdir argument, my questions would be as
follows:
1) Could such change break something that I might have missed?
2) Would you be willing to accept this patch for versions prior to 12?
Thanks in advance.
--
Patrik Novotný
Associate Software Engineer
Red Hat
panovotn(at)redhat(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2019-09-10 13:10:57 | Re: Avoiding hash join batch explosions with extreme skew and weird stats |
Previous Message | Alvaro Herrera from 2ndQuadrant | 2019-09-10 12:30:17 | Re: [bug fix] Produce a crash dump before main() on Windows |