Re: new notify payload as string - Mailing list pgsql-hackers

From Tom Lane
Subject Re: new notify payload as string
Date
Msg-id 24066.1282765394@sss.pgh.pa.us
Whole thread Raw
In response to new notify payload as string  ("A.M." <agentm@themactionfaction.com>)
List pgsql-hackers
"A.M." <agentm@themactionfaction.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


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Python 2.7 deprecated the PyCObject API?
Next
From: Oleg Bartunov
Date:
Subject: Re: No documentation for filtering dictionary feature?