| From: | Josh <josh(at)schemaverse(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, mmoncure(at)gmail(dot)com |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5911: pg_notify() function only works when channel name is lower case |
| Date: | 2011-03-03 16:41:22 |
| Message-ID: | 4D6FC4B2.2090109@schemaverse.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Thank you both for clearing that up (and doing so quite quickly!).
The behavior makes complete sense now that I understand what is
happening here behind the scenes.
Regards,
Josh
On 3/3/2011 11:24 AM, Tom Lane wrote:
> "Joshua McDougall"<josh(at)schemaverse(dot)com> writes:
>> When using the pg_notify(text,text) function, the channel name MUST be lower
>> case otherwise the message does not go through.
> It's not clear to me that this is a bug. The argument of NOTIFY is a
> SQL identifier, which is folded to lower case by the lexer if not
> double-quoted, but the argument of pg_notify is a string constant which
> is a different matter altogether.
>
> We could have pg_notify lowercase its argument at runtime, but then
> we'd have to introduce quoting rules, so that you could do
>
> select pg_notify('"IntentionallyMixedCase"', '...');
>
> This isn't a lot clearer than the current behavior, and it definitely
> wouldn't be backwards compatible. So I'm inclined to leave it alone.
>
> regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Schmitt | 2011-03-03 16:51:13 | Re: BUG #5869: postgresql corrupts unquoted non-ascii chars in column aliases |
| Previous Message | Jakub Ouhrabka | 2011-03-03 16:39:57 | Re: Corrupted index on 9.0.3 streaming hot standby |