Re: [COMMITTERS] pgsql: Explicitly bind gettext to the correct encoding on Windows.

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [COMMITTERS] pgsql: Explicitly bind gettext to the correct encoding on Windows.
Date: 2009-02-15 14:08:51
Message-ID: 499821F3.7050004@hagander.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Tom Lane wrote:
> mha(at)postgresql(dot)org (Magnus Hagander) writes:
>> Explicitly bind gettext to the correct encoding on Windows.
>
> I have a couple of objections to this patch. First, what happens if
> it fails to find a matching table entry? (The existing answer is
> "nothing", but that doesn't seem right.) Second and more critical,
> it adds still another data structure that has to be maintained when
> the list of encodings changes, and it doesn't even live in the same
> file as any existing encoding-information table.
>
> 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?

//Magnus

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2009-02-15 17:21:54 Re: [COMMITTERS] pgsql: Explicitly bind gettext to the correct encoding on Windows.
Previous Message Magnus Hagander 2009-02-15 13:58:22 pgsql: Loop calling CallNamedPipe() several times in case it fails,

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-02-15 17:21:54 Re: [COMMITTERS] pgsql: Explicitly bind gettext to the correct encoding on Windows.
Previous Message Simon Riggs 2009-02-15 10:18:10 Re: Database corruption help