pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
To: Magnus Hagander <magnus@hagander.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgreSQL.org
Subject: Re: Re: [COMMITTERS] pgsql: Explicitly bind gettext to the correct encoding on Windows.
Date: Wed, 08 Apr 2009 13:36:01 +0300
Message-ID: <49DC7E11.2050501@enterprisedb.com> (raw)
In-Reply-To: <49D47C40.5040300@hagander.net>
References: <20090122100948.89F977559ED@cvs.postgresql.org>
	<20643.1232666867@sss.pgh.pa.us>
	<499821F3.7050004@hagander.net>
	<22474.1234718514@sss.pgh.pa.us>
	<49D47C40.5040300@hagander.net>

Magnus Hagander wrote:
> Tom Lane wrote:
>> Magnus Hagander <magnus@hagander.net> writes:
>>> Tom Lane wrote:
>>>> What makes more sense to me is to add a table to encnames.c that
>>>> provides the gettext name of every encoding that we support.
>>> Do you mean a separate table there, or should we add a new column to one
>>> of the existing tables?
>> Whichever seems to make more sense is fine with me.  I just don't want
>> add-an-encoding maintenance requirements spread across N different
>> source files.
> 
> I was about to start looking at this when that other thread
> (http://archives.postgresql.org//pgsql-hackers/2009-03/msg01270.php)
> started about related issues on other platforms. Seems we should have a
> "coordinated fix" for this, so I'm going to want and see what come sout
> of that one. Unless I'm misunderstanding thigns and they're not related?

I've committed a fairly trivial patch per Peter's suggestion to fix the 
other thread's issue. I left the table as is, so whatever refactorings 
were planned can now be applied.

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com



view thread (12+ messages)  latest in thread

Message-ID: <49DC7E11.2050501@enterprisedb.com>
Permalink:  ../49DC7E11.2050501@enterprisedb.com/
Also on:    postgresql.org/message-id/49DC7E11.2050501@enterprisedb.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-committers@postgresql.org
  Cc: heikki.linnakangas@enterprisedb.com, magnus@hagander.net, tgl@sss.pgh.pa.us, pgsql-hackers@postgreSQL.org
  Subject: Re: Re: [COMMITTERS] pgsql: Explicitly bind gettext to the correct encoding on Windows.
  In-Reply-To: <49DC7E11.2050501@enterprisedb.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox