Re: Notiffy problem - Mailing list pgsql-general

From Tom Lane
Subject Re: Notiffy problem
Date
Msg-id 24228.1340982615@sss.pgh.pa.us
Whole thread Raw
In response to Re: Notiffy problem  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: Notiffy problem
List pgsql-general
Merlin Moncure <mmoncure@gmail.com> writes:
> On Fri, Jun 29, 2012 at 8:58 AM, adasko98 <adasko.86@gmail.com> wrote:
>>>>     Notify demoApp, n_user ;<----here is a problem

>>> Looks like a limitation of the plpgsql parser, perhaps even counts as a
>>> bug.

It is not a bug, but a documented limitation of the NOTIFY command: the
payload has to be a simple string literal.

(The technical reason for that is that NOTIFY isn't a plannable
statement, but a utility command, and utility commands generally don't
evaluate expressions.  In principle we could fix that, but in practice
it's not going to change, because the pg_notify() function serves just
fine for every case where you want a non-constant payload.)

            regards, tom lane

pgsql-general by date:

Previous
From: Patrick Schneider
Date:
Subject: Conversion of columns during CSV Import
Next
From: Raymond O'Donnell
Date:
Subject: Re: Conversion of columns during CSV Import