Prev: default parameters
Next: Large object dumps vs older pg_restore
From: "David E. Wheeler" on 17 Feb 2010 15:50
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


--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: "David E. Wheeler" on 18 Feb 2010 16:56
On Feb 18, 2010, at 1:01 PM, Greg Sabino Mullane wrote:

>> Is the payload decoded to utf8 when pg_enable_utf8 is true?
>
> No - there's a note in the code to look into that at some point. So
> stick to ASCII for the moment. I'm sure the great DBD::Pg utf-8
> overhaul (where we get rid of the pg_enable_utf8 hack) will encompass
> payloads as well.

Is that immanent?

Best,

David

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

 | 
Pages: 1
Prev: default parameters
Next: Large object dumps vs older pg_restore