From: | Daniel Farina <daniel(at)heroku(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: --disable-shared is entirely broken these days |
Date: | 2012-05-27 01:00:32 |
Message-ID: | CAAZKuFZwqkJzqwhWDS98acWUeh2+=A1TPEUv6YVGZJsO2y4+gQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, May 26, 2012 at 12:53 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 2. Seeing that this is the first complaint since 9.0, should we decide
> that --disable-shared is no longer worth supporting? Seems like we
> should either make this case work or remove this switch. I notice
> that the switch isn't documented anywhere in the SGML docs, either.
> If we do keep it, we'd better document that it results in a severely
> crippled version of Postgres.
I can't really imagine the reasons to support this switch at this
time. Compile times are fast, disk space cheap, and if one wanted to
avoid the dynamic linker entirely and use features like replication
(which, IIRC, is dynamically linked for libpqwalreceiver.so) and
plpgsql then people are out of luck without some work of (perhaps?)
questionable value.
--
fdr
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2012-05-27 03:16:20 | Re: VIP: new format for psql - shell - simple using psql in shell |
Previous Message | Tom Lane | 2012-05-26 19:53:33 | --disable-shared is entirely broken these days |