pgsql: Set client encoding explicitly in plpython_unicode test

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Set client encoding explicitly in plpython_unicode test
Date: 2011-04-16 18:54:00
Message-ID: E1QBAd6-0000zd-5h@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Set client encoding explicitly in plpython_unicode test

This will (hopefully) eliminate the need for the
plpython_unicode_0.out expected file.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/5809a6458450a59f8c4a7a25beaefc81cff563d1

Modified Files
--------------
src/pl/plpython/expected/README | 3 +-
src/pl/plpython/expected/plpython_unicode.out | 1 +
src/pl/plpython/expected/plpython_unicode_0.out | 50 -----------------------
src/pl/plpython/expected/plpython_unicode_3.out | 1 +
src/pl/plpython/sql/plpython_unicode.sql | 2 +
5 files changed, 5 insertions(+), 52 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2011-04-16 19:07:39 Re: [COMMITTERS] pgsql: Rename pg_regress option --multibyte to --encoding
Previous Message Tom Lane 2011-04-16 00:19:44 pgsql: Prevent incorrect updates of pg_index while reindexing pg_index