Skip site navigation (1) Skip section navigation (2)

Re: prevent encoding conversion recursive error

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>,Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>, pgsql-patches(at)postgresql(dot)org
Subject: Re: prevent encoding conversion recursive error
Date: 2005-09-01 15:48:55
Message-ID: 200509011748.56565.peter_e@gmx.net (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Am Sonntag, 21. August 2005 01:48 schrieb Tom Lane:
> One thing that occurred to me is that we might be able to simplify the
> problem by adopting a project standard that all NLS message files shall
> be in UTF8, period.  Then we only have one encoding name to figure out
> rather than N.  Maybe this doesn't help much ...

I suppose this would then break NLS on Windows, no?

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/

In response to

Responses

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2005-09-01 15:56:10
Subject: Re: Remove xmin and cmin from frozen tuples
Previous:From: Sergey E. KoposovDate: 2005-09-01 15:44:34
Subject: Re: 8.1beta, Subtle bug in COPY in Solaris systems

pgsql-patches by date

Next:From: Alvaro HerreraDate: 2005-09-01 16:31:25
Subject: Re: Version number in psql banner
Previous:From: Peter EisentrautDate: 2005-09-01 15:30:34
Subject: Version number in psql banner

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group