From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: upgrade failure from 9.5 to head |
Date: | 2015-07-29 15:06:43 |
Message-ID: | 29554.1438182403@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Andres Freund (andres(at)anarazel(dot)de) wrote:
>> Hm. That issue doesn't particularly concern me. Having all .so's
>> available in the installation seems like a pretty basic
>> requirement. Security labels are by far not the only things that'll fail
>> without an extension's .so present, no?
> It's certainly an issue that postgis users are familiar with.
Really? What aspect of postgis requires mucking with
shared_preload_libraries?
If you ask me, shared_preload_libraries was only ever meant as a
performance optimization. If user-visible DDL behavior depends on a
library being preloaded that way, that feature is broken. There
are some cases where we probably don't care enough to provide a
proper solution, but I'm not sure why we would think that security
labels fall in the don't-really-give-a-damn-if-it-works class.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2015-07-29 15:08:29 | Re: upgrade failure from 9.5 to head |
Previous Message | Tom Lane | 2015-07-29 15:01:40 | Re: upgrade failure from 9.5 to head |