Greg Smith <g...@2ndquadrant.com> writes:
> The only other item related to this view on the TODO was "Have
> pg_stat_activity display query strings in the correct client encoding".
> That might be worthwhile to bundle into this rework, but it doesn't seem
> something that impacts the UI such that it must be considered early.
That entry is garbled to the point of uselessness anyway, as client
encoding has got exactly zip to do with it. The point is that another
backend's entry could be in a different *server* encoding, and what do
you do if there's no equivalent character in your encoding?
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
