From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | --disable-shared is entirely broken these days |
Date: | 2012-05-26 19:53:33 |
Message-ID: | 28202.1338062013@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
A gripe today in pgsql-novice made me realize that configure's
--disable-shared option has been useless since 9.0, because it prevents
plpgsql.so from being built, which causes initdb to fail now that
plpgsql is installed "by default" --- which actually seems to mean
"you don't have any choice about whether to install it".
So, a few questions:
1. Should we honor the promise implicit in the "by default" wording
that there should be a way to initdb without plpgsql?
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Farina | 2012-05-27 01:00:32 | Re: --disable-shared is entirely broken these days |
Previous Message | Tom Lane | 2012-05-26 19:14:18 | Synchronized scans versus relcache reinitialization |