Re: [HACKERS] [pgsql-translators] pg_upgrade translation - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [HACKERS] [pgsql-translators] pg_upgrade translation
Date
Msg-id 20170528183903.qsre2kzbyxhfhauk@alvherre.pgsql
Whole thread Raw
In response to [HACKERS] pg_upgrade translation  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
Alvaro Herrera wrote:
> Translatability was turned on for pg_upgrade on pg10, but it needs some
> work.  The choices are we fix it now, or we revert the addition of NLS
> there and we do it for PG11.

Here are two patches to fix the messages, replacing "new" with "target"
and "old" with "source".  I was going to do just the first one
initially, but I figured that the output would become wildly
inconsistent if I stopped at that point.

Now we still have one inconsistency left: the command-line options
--old-bindir --new-datadir etc all contain the words "new" and "old".
Same with a bunch of environment variables.  I think the real solution
is that we should change those to --source-bindir and --target-datadir
respectively (and the other ones continue to work for backwards
compatibility), but then maybe leave them alone.

I'll continue fixing things.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Allow GiST opcalsses without compress\decompres functions
Next
From: Andrew Borodin
Date:
Subject: Re: [HACKERS] Allow GiST opcalsses without compress\decompres functions