Magnus Hagander writes:
> Tom Lane wrote:
>> Comments?
> Certainly seems like a reasonable compromise. From what I understand,
> you'll get this "failed to commit..." message *if* you have changedf
> things in pg_conversion. I think that's acceptable - it's not like
> people modify pg_conversion
Tom Lane wrote:
> A problem with such caching is that it'd fail to respond to changes in
> the content of pg_conversion. Now the code is already pretty
> insensitive in that respect, because if you're not doing any fresh "SET
> client_encoding" commands it won't ever notice changes in that catalog
I think I see the reason for the recent report of $SUBJECT.
Starting with a client_encoding different from server_encoding,
change it to something else and then roll back, for example
u8=# show server_encoding ;
server_encoding
-
UTF8
(1 row)
u8=# set client_encoding to latin1;
