Re: BUG #14028: FATAL: cannot perform encoding conversion outside a transaction

From: Noah Misch <noah(at)leadboat(dot)com>
To: Srivathson KK <srivathson(dot)k(at)zohocorp(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "<pgsql-bugs(at)postgresql(dot)org>" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14028: FATAL: cannot perform encoding conversion outside a transaction
Date: 2016-04-10 20:55:21
Message-ID: 20160410205521.GA1779466@tornado.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Mar 21, 2016 at 04:32:43PM +0530, Srivathson KK wrote:
> Btw, may I know why it is still in Todo list?

I assume you mean this TODO item:

|Windows: Cache MessageEncoding conversion for use outside transactions
* http://www.postgresql.org/message-id/20150812055719.GA1945333@tornado.leadboat.com

The changes in 9.4.5 stopped the "cannot perform encoding conversion outside a
transaction" errors and fixed things completely for Korean-locale databases.
For a database encoding having no Windows code page, such LATIN8, we still
make mojibake with a non-ASCII message written outside a transaction. The
TODO item would fix that.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message duncan.stokes 2016-04-10 22:07:38 BUG #14082: Unexpected time adjustment for output using "at time zone"
Previous Message David G. Johnston 2016-04-10 16:13:20 Re: BUG #14079: Issues with query