Re: Fix for pg_upgrade's forcing pg_controldata into English - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Fix for pg_upgrade's forcing pg_controldata into English
Date
Msg-id 1283373680-sup-9235@alvh.no-ip.org
Whole thread Raw
In response to Fix for pg_upgrade's forcing pg_controldata into English  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Fix for pg_upgrade's forcing pg_controldata into English  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Synchronous replication - patch status inquiry
Next
From: Tom Lane
Date:
Subject: Re: Fix for pg_upgrade's forcing pg_controldata into English