From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: default_language |
Date: | 2010-01-25 14:51:17 |
Message-ID: | AF3DFE3C835DB1D1B73274FD@[172.26.14.62] |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
--On 25. Januar 2010 09:30:56 -0500 Robert Haas <robertmhaas(at)gmail(dot)com>
wrote:
> This will turn into
> another setting like search_path and standard_conforming_strings that
> can break working code if the actual value doesn't match the
> anticipated value. I can't figure out why someone would want to use
> this even if we had it.
>
Hmm, even search_path is currently more strict than default_do_language
when used interactively:
bernd(at)localhost:bernd #= SET search_path TO 'nonexistingschema';
ERROR: schema "nonexistingschema" does not exist
bernd(at)localhost:bernd #= SET default_do_language TO 'blabla';
SET
Doesn't make sense to me...
--
Thanks
Bernd
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2010-01-25 14:52:45 | Re: pg_listener entries deleted under heavy NOTIFY load only on Windows |
Previous Message | Simon Riggs | 2010-01-25 14:40:29 | Re: default_language |