pgsql: Fix translatability markings in psql, and add defenses against f - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Fix translatability markings in psql, and add defenses against f
Date
Msg-id E1VzYPf-0002dC-Up@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix translatability markings in psql, and add defenses against future bugs.

Several previous commits have added columns to various \d queries without
updating their translate_columns[] arrays, leading to potentially incorrect
translations in NLS-enabled builds.  Offenders include commit 893686762
(added prosecdef to \df+), c9ac00e6e (added description to \dc+) and
3b17efdfd (added description to \dC+).  Fix those cases back to 9.3 or
9.2 as appropriate.

Since this is evidently more easily missed than one would like, in HEAD
also add an Assert that the supplied array is long enough.  This requires
an API change for printQuery(), so it seems inappropriate for back
branches, but presumably all future changes will be tested in HEAD anyway.

In HEAD and 9.3, also clean up a whole lot of sloppiness in the emitted
SQL for \dy (event triggers): lack of translatability due to failing to
pass words-to-be-translated through gettext_noop(), inadequate schema
qualification, and sloppy formatting resulting in unnecessarily ugly
-E output.

Peter Eisentraut and Tom Lane, per bug #8702 from Sergey Burladyan

Branch
------
REL9_2_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/fa28f9cba889335ea68f9326010ae008f1d97b74

Modified Files
--------------
src/bin/psql/describe.c |    5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Fix translatability markings in psql, and add defenses against f
Next
From: Tom Lane
Date:
Subject: pgsql: Fix translatability markings in psql, and add defenses against f