-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160
>> 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? Barring sudden free time, funding, and/or a client request, no. - -- Greg Sabino Mullane g...@turnstep.com End Point Corporation http://www.endpoint.com/ PGP Key: 0x14964AC8 201002181711 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAkt9u0AACgkQvJuQZxSWSsj/8wCcD6qwNvnRoQ+UJWzDuAIM1vh/ 7pQAn1yRdO1bKL1qLpX8OeggS4iCl+1j =sOJR -----END PGP SIGNATURE----- -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers