Skip site navigation (1) Skip section navigation (2)

Re: new notify payload as string

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: new notify payload as string
Date: 2010-08-25 19:43:14
Message-ID: 24066.1282765394@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
"A.M." <agentm(at)themactionfaction(dot)com> writes:
> So, it is impossible to differentiate between a notification with an
> empty string payload and a notification without a payload due to the
> backend protocol defining the payload as a string.

That's correct.  This was baked into the FE/BE protocol in 2003;
we're not going to change it now, especially not without a pretty
convincing argument why it's critical functionality to have.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Oleg BartunovDate: 2010-08-25 20:22:49
Subject: Re: No documentation for filtering dictionary feature?
Previous:From: Peter EisentrautDate: 2010-08-25 19:39:19
Subject: Re: Python 2.7 deprecated the PyCObject API?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group