From: Tom Lane <tgl@sss.pgh.pa.us>
To: Axel Rau <Axel.Rau@chaos1.de>
cc: pgsql-sql@lists.postgresql.org
Subject: Re: Restrictions of channel arg of pg_notofy
In-reply-to: <E5B1FE41-D93A-4CA3-8754-1650A90CBFAD@Chaos1.DE>
References: <023C223F-4FC9-4E9E-A8C6-17F491358FA7@Chaos1.DE>
 <28634.1556391117@sss.pgh.pa.us>
 <E5B1FE41-D93A-4CA3-8754-1650A90CBFAD@Chaos1.DE>
Comments: In-reply-to Axel Rau <Axel.Rau@chaos1.de>
	message dated "Sun, 28 Apr 2019 18:22:12 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <11071.1556470926.1@sss.pgh.pa.us>
Date: Sun, 28 Apr 2019 13:02:06 -0400
Message-ID: <11072.1556470926@sss.pgh.pa.us>
Precedence: bulk

Axel Rau <Axel.Rau@chaos1.de> writes:
> I have investigated further:
> pg_notify does not work at all, even with a constant string channel arg.
> NOTIFY works.
> This is release 11.2.

[ shrug... ]  Works for me.

> What am I doing wrong?

Hard to tell when you haven't provided a complete example.

Just looking at the code you did show, though, I notice that
you have

    PERFORM pg_notify(fac);

but there's no single-argument form of pg_notify in standard PG:

regression=# \df pg_notify
                           List of functions
   Schema   |   Name    | Result data type | Argument data types | Type 
------------+-----------+------------------+---------------------+------
 pg_catalog | pg_notify | void             | text, text          | func
(1 row)

Maybe whatever shim you've got for that doesn't work right?

			regards, tom lane