Re: pg_stats queries versus per-database encodings

Tom Lane wrote:
> Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> > Tom Lane wrote:
> >> We could attack this by including source database's encoding in the
> >> shared-memory entries, and performing a conversion on the fly when
> >> reading out the data.  However, what happens if the conversion fails?
> 
> > The most useful behavior would be to replace the untranslatable 
> > characters with "?". I'm not sure how invasive the changes to the 
> > conversion functions would be to support that.
> 
> I agree, but it looks like fairly massive changes would be needed,
> starting with redefining the API for conversion functions to add
> an error/noerror boolean.  Not something that I care to tackle
> right now.  Maybe we shall just have to live with it for another
> release.

Added to TODO:
Have pg_stat_activity display query strings in the correct clientencoding    *
http://archives.postgresql.org/pgsql-hackers/2009-01/msg00131.php
 

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +