On Wed, Sep 7, 2011 at 22:42, Alvaro Herrera <alvhe...@commandprompt.com> wrote: > A mishandled encoding conversion could be problematic, so that needs to > be carefully considered (perhaps just shut off unconditionally).
Are you referring to log file encoding or something else? The log file is already potentially mixed-encoding, as different databases may have different encodings and backends just dump bytes to it in their current encoding. pg_verify_mbstr() could potentially be used with noError=true if we can figure out the backend's current encoding, but that indeed sounds like something to avoid. Regards, Marti -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
