From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Axel Rau <Axel(dot)Rau(at)Chaos1(dot)DE> |
Cc: | pgsql-sql(at)lists(dot)postgresql(dot)org |
Subject: | Re: Restrictions of channel arg of pg_notofy |
Date: | 2019-04-28 18:23:16 |
Message-ID: | 15104.1556475796@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Axel Rau <Axel(dot)Rau(at)Chaos1(dot)DE> writes:
>> Am 28.04.2019 um 19:02 schrieb Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us <mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us>>:
>>> Hard to tell when you haven't provided a complete example.
>> This is my test case with constant string:
>> CREATE OR REPLACE FUNCTION syslog.new_event_action() RETURNS trigger
>> LANGUAGE plpgsql
>> AS $$
>> BEGIN
>> RAISE WARNING 'syslog.new_event_action() called.';
>> PERFORM pg_notify('INSERTED', '');
>> RETURN NEW;
>> END
>> $$;
>>
>> The warning is being logged.
>>
>> In psql session 1, I run a LISTEN INSERTED;
If you're typing it exactly like that, you have a case-folding problem.
Try
LISTEN "INSERTED";
instead, or make the pg_notify argument lower-case.
However, that doesn't seem like it would explain your original problem,
since that didn't involve upper-case letters.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Axel Rau | 2019-04-29 08:23:50 | [RESOLVED] Re: Restrictions of channel arg of pg_notofy |
Previous Message | Axel Rau | 2019-04-28 17:46:12 | Re: Restrictions of channel arg of pg_notofy |