Scott Marlowe <scott.marl...@gmail.com> writes:
> On Tue, Nov 24, 2009 at 11:34 AM, Tom Lane <t...@sss.pgh.pa.us> wrote:
>> The point would be to reduce the risk that you're changing the language
>> definition in a surprising way. Extra args would imply that you're
>> trying to install a non-default definition of the language.
> But if you'd installed it that way before, wouldn't you then need the
> arguments this time to have them match?
If you knew you'd installed it that way before, you wouldn't be
executing this command at all. The use-case for commands like this
IMO is scripts that don't know exactly what the database state is.
The use-case for a script that is installing non-default language
parameters into somebody else's database seems pretty darn thin.
I'm not dead set on this by any means. But it seems like it would
help reduce the risk of bad consequences from CREATE OR REPLACE
LANGUAGE.
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
