parametrized NOTIFY - issue in plpgsql, maybe ToDo - Mailing list pgsql-hackers

From Pavel Stehule
Subject parametrized NOTIFY - issue in plpgsql, maybe ToDo
Date
Msg-id 162867791003161223y52ec7618v417429e91281331@mail.gmail.com
Whole thread Raw
Responses Re: parametrized NOTIFY - issue in plpgsql, maybe ToDo  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hello

I am testing NOTIFY statement. It have to be used from plpgsql via
EXECUTE, because doesn't support paramaters.

Can be it documented somewhere?

create or replace function foo(a varchar)
returns void as $$
begin execute 'notify xxx, ' || quote_literal(a); return;
end;
$$ language plpgsql;
CREATE FUNCTION
Time: 2,513 ms
pavel@postgres:5432=# select foo('pavel');foo
-----

(1 row)

Time: 31,732 ms
pavel@postgres:5432=# listen xxx;
LISTEN
Time: 0,271 ms
pavel@postgres:5432=# select foo('pavel');foo
-----

(1 row)

Time: 436,058 ms
Asynchronous notification "xxx" with payload "pavel" received from
server process with PID 4730.
pavel@postgres:5432=#


pgsql-hackers by date:

Previous
From: Gokulakannan Somasundaram
Date:
Subject: Re: Bug in 9.0Alpha4
Next
From: Tom Lane
Date:
Subject: Re: parametrized NOTIFY - issue in plpgsql, maybe ToDo