Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > Understood. In fact, after having a look at this patch and giving it a
> > little refactoring I think it's pretty obvious; right now we're calling
> > bind_textdomain_codeset only for the main domain, and with this patch we
> > also set it for all other domains we use.
> More generally, should we push the bindtextdomain calls themselves into
> the new function (and perhaps call it something else than
> SetDomainCodeSet)? Seems like logically this should be thought of as
> all one operation, ie, it's not clear to me that it ever makes sense to
> call bindtextdomain without also worrying about encoding.
I'm not sure that can be made to work easily. On the backend itself we
call bindtextdomain in set_pglocale_pgservice() which is also used by
programs in src/bin/. Shuffling things in there would be more involved
than seems worth.
As for names, how about pg_bind_textdomain_codeset?
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
In response to
pgsql-hackers by date
|Next:||From: Dickson S. Guedes||Date: 2009-03-07 23:54:49|
|Subject: ERROR: "failed to locate grouping columns"|
|Previous:||From: Andrew Dunstan||Date: 2009-03-07 23:51:08|
|Subject: Re: small parallel restore optimization|
pgsql-committers by date
|Next:||From: Hiroshi Saito||Date: 2009-03-08 01:58:42|
|Subject: Re: Re: [COMMITTERS] pgsql: Redefine _() to dgettext()instead of gettext() so that it uses|
|Previous:||From: Tom Lane||Date: 2009-03-07 23:06:16|
|Subject: Re: Re: [COMMITTERS] pgsql: Redefine _() to dgettext() instead of gettext() so that it uses |