| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: default_language |
| Date: | 2010-01-25 00:13:13 |
| Message-ID: | 4B5CE219.90604@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greg Stark wrote:
> On Sun, Jan 24, 2010 at 11:18 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>
>> I would prefer having the option, but removing it completely does at
>> least solve the bizarre inconsistency I've highlighted.
>>
>>
>
> I don't see it as much of an inconsistency. The whole point of DO is
> to be convenient, whereas CREATE FUNCTION is DDL for defining what
> your database looks like and it should be well defined in perpetuity.
>
> However it's also possible will write DO blocks into their application
> code in which case it might be preferable not to have a
> default_language GUC which would have to be set correctly for the code
> to work.
>
Yeah, it's the possibility of scripts or functions with embedded DO
statements that makes me think we'd be better off without a setting for
this.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Baron Schwartz | 2010-01-25 00:16:23 | Re: MySQL-ism help patch for psql |
| Previous Message | Greg Stark | 2010-01-24 23:59:05 | Re: default_language |