Thread: Re: [HACKERS] Listen/Notify payload and interfaces

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


> With the new listen/notify implementation we can send a payload along
> with the notification. This has been in the protocol already since
> years and there is no change needed for libpq. However we need to
> adapt the various interfaces to allow a payload to be sent and
> received.

DBD::Pg has been ready since 2008, if you need something to test with. :)

Usage is:

while (my $notify = $dbh->pg_notifies) { my ($name, $pid, $payload) = @$notify; print qq{I received notice "$name" from
PID$pid, payload was "$payload"\n};                                            
 
}

Not sure what you mean by adapting interfaces to send payloads, I imagine 
most if not all simply require a NOTIFY to be sent via PQexec.

- -- 
Greg Sabino Mullane greg@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201002171302
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAkt8L3oACgkQvJuQZxSWSsik0wCfZexc8ZU2/zo4JZQ47YblKend
yEMAoLdG4IS3pc163UVSpQ11/de+xzUT
=dx6+
-----END PGP SIGNATURE-----

On Feb 17, 2010, at 10:04 AM, Greg Sabino Mullane wrote:

> while (my $notify = $dbh->pg_notifies) {
>  my ($name, $pid, $payload) = @$notify;
>  print qq{I received notice "$name" from PID $pid, payload was "$payload"\n};
> }
>
> Not sure what you mean by adapting interfaces to send payloads, I imagine
> most if not all simply require a NOTIFY to be sent via PQexec.

Is the payload decoded to utf8 when pg_enable_utf8 is true?

Best,

David