Re: warn if GUC set to an invalid shared library
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: Maciek Sakrejda <m.sakrejda@gmail.com>,
Robert Haas <robertmhaas@gmail.com>,
"David G. Johnston" <david.g.johnston@gmail.com>,
Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>,
Cary Huang <cary.huang@highgo.ca>, pgsql-hackers@lists.postgresql.org
Date: 2022-10-31T13:43:05Z
Lists: pgsql-hackers
Justin Pryzby <pryzby@telsasoft.com> writes: > On Sun, Oct 30, 2022 at 04:12:33PM -0700, Maciek Sakrejda wrote: >> Also, for what it's worth, I think requiring the libraries to be in >> place before running ALTER SYSTEM does not really seem that onerous. I >> can't really think of use cases it precludes. > Right now, it's allowed to set the GUC before installing the shlib. > That's a supported case (see the 11 month old messages toward the > beginning of this thread). Yeah, I am afraid that you will break assorted dump/restore and pg_upgrade scenarios if you insist on that. regards, tom lane