Excerpts from Bruce Momjian's message of mié sep 01 16:35:18 -0400 2010:

> I have implemented your suggestion of setting LANG, LANGUAGE, and
> LC_MESSAGES based on code in pg_regress.c;  that is the only place I see
> where we force English, and it certainly has received more testing.

I think a real long-term solution is to have a machine-readable format
for pg_controldata, perhaps something very simple like

$ pg_controldata --machine
PGCONTROL_VERSION_NUMBER=903
CATALOG_VERSION_NUMBER=201008051
DATABASE_SYSIDENTIFIER=5504177303240039672
etc

This wouldn't be subject to translation and thus much easier to process.

-- 
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

• Fix for pg_upgrade's forcing pg_controldata into English at 2010-09-01 20:35:18 from Bruce Momjian

Responses

• Re: Fix for pg_upgrade's forcing pg_controldata into English at 2010-09-01 20:51:06 from Tom Lane

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2010-09-01 20:51:06
	Subject: Re: Fix for pg_upgrade's forcing pg_controldata into English
Previous:	From: Simon Riggs	Date: 2010-09-01 20:43:01
	Subject: Re: Synchronous replication - patch status inquiry