From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Sabino Mullane <greg(at)turnstep(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Fix for pg_upgrade's forcing pg_controldata into English |
Date: | 2010-09-01 20:44:34 |
Message-ID: | 1283373680-sup-9235@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-09-01 20:51:06 | Re: Fix for pg_upgrade's forcing pg_controldata into English |
Previous Message | Simon Riggs | 2010-09-01 20:43:01 | Re: Synchronous replication - patch status inquiry |