From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
Cc: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, PGSQL Mailing List <pgsql-general(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org, Bruce Momjian <bruce(at)momjian(dot)us>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Robert Haas <robertmhaas(at)gmail(dot)com>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Thom Brown <thombrown(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
Subject: | Re: [HACKERS] Installing PL/pgSQL by default |
Date: | 2009-12-07 15:03:41 |
Message-ID: | 3979.1260198221@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Dimitri Fontaine <dfontaine(at)hi-media(dot)com> writes:
> So should the decision to remove plpgsql be on the hosting platform
> hands or the hosted database owner?
Why not? If they really want to prohibit use of a feature the upstream
project has decided should be standard, that's their privilege.
The argument against seems to be basically "this should work exactly
like it did before", but if that's the standard then we can never
have plpgsql installed by default at all.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Verite | 2009-12-07 15:06:04 | Re: Error_startup postgresql server |
Previous Message | Roberto Mello | 2009-12-07 14:58:32 | Re: New PostgreSQL Committers |
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2009-12-07 15:06:08 | Re: New PostgreSQL Committers |
Previous Message | Roberto Mello | 2009-12-07 14:58:32 | Re: New PostgreSQL Committers |