pgsql: On second thought, the tests for what to do with stderr output

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: On second thought, the tests for what to do with stderr output
Date: 2007-07-19 21:58:12
Message-ID: 20070719215812.F06AA9FB731@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
On second thought, the tests for what to do with stderr output are a
lot more sensible if we check the chunk-output case first. Not
back-patched since it's just a cosmetic improvement.

Modified Files:
--------------
pgsql/src/backend/utils/error:
elog.c (r1.188 -> r1.189)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/error/elog.c.diff?r1=1.188&r2=1.189)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2007-07-20 16:23:34 pgsql: Capitalize language key words in error messages
Previous Message Tom Lane 2007-07-19 20:34:54 pgsql: Make replace(), split_part(), and string_to_array() behave