From: | Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Revert part of the previous patch that avoided using PLy_elog(). |
Date: | 2012-07-05 20:50:44 |
Message-ID: | E1Smt0e-0007rN-6O@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Revert part of the previous patch that avoided using PLy_elog().
That caused the plpython_unicode regression test to fail on SQL_ASCII
encoding, as evidenced by the buildfarm. The reason is that with the patch,
you don't get the detail in the error message that you got before. That
detail is actually very informative, so rather than just adjust the expected
output, let's revert that part of the patch for now to make the buildfarm
green again, and figure out some other way to avoid the recursion of
PLy_elog() that doesn't lose the detail.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/de479e2ed28925ddd2907cad3e2d5dddd3b97199
Modified Files
--------------
src/pl/plpython/plpy_util.c | 11 +----------
1 files changed, 1 insertions(+), 10 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Urbański | 2012-07-05 20:53:24 | Re: [COMMITTERS] pgsql: Fix mapping of PostgreSQL encodings to Python encodings. |
Previous Message | Heikki Linnakangas | 2012-07-05 20:37:19 | Re: [COMMITTERS] pgsql: Fix mapping of PostgreSQL encodings to Python encodings. |