| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Gregg Jaskiewicz <gryzman(at)gmail(dot)com> |
| Cc: | Thom Brown <thom(at)linux(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: language name case sensitivity, also known as plpgsql <> 'PLpgSQL' |
| Date: | 2012-03-26 17:27:38 |
| Message-ID: | 13217.1332782858@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Gregg Jaskiewicz <gryzman(at)gmail(dot)com> writes:
> On 26 March 2012 16:41, Thom Brown <thom(at)linux(dot)com> wrote:
>> Probably something to do with this:
>> http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=67dc4eed42186ba6a2456578899bfd38d003201a
> Would you call it a regression ?
It's an intentional change to make handling of language names less
bizarrely different from every other name in SQL. Personally, I'd
recommend getting rid of the single quotes. Use of a string literal for
a language name has been poor style since 7.2 or thereabouts, and it is
foreseeable that at some point we'd stop accepting string literals for
this purpose altogether.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Norberto Dellê | 2012-03-26 18:54:52 | pgstat wait timeout |
| Previous Message | Gregg Jaskiewicz | 2012-03-26 15:47:53 | Re: language name case sensitivity, also known as plpgsql <> 'PLpgSQL' |