| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | adasko98 <adasko(dot)86(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Notiffy problem |
| Date: | 2012-06-29 15:10:15 |
| Message-ID: | 24228.1340982615@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> On Fri, Jun 29, 2012 at 8:58 AM, adasko98 <adasko(dot)86(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Raymond O'Donnell | 2012-06-29 17:10:26 | Re: Conversion of columns during CSV Import |
| Previous Message | Merlin Moncure | 2012-06-29 14:53:33 | Re: Notiffy problem |