Paul Ramsey <pram...@cleverelephant.ca> writes:
> On August 20, 2015 at 2:17:31 AM, Simon Riggs
> (si...@2ndquadrant.com(mailto:si...@2ndquadrant.com)) wrote:
>> Sounds like we need RedefineCustomStringVariable()Â
> Yes, if that had existed we would not have had any problems (as long as it
> delegated back to Define..() in the case where the variable hadnât been
> created yetâ¦, since one of the problems is knowing if/to-what-extent a
> custom variable has already been defined).
I'm not sure that the situation you describe can be expected to work
reliably; the problems are far wider than just GUC variables. If two
different .so's are exposing broadly the same set of C function names,
how can we be sure which one will get called by the dynamic linker?
Isn't it likely that we'd end up continuing to call some functions
out of the old .so, probably leading to disaster?
I don't necessarily object to providing some solution for GUCs, but
I think first we need to question whether that isn't just the tip of
a large iceberg.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
