From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Jim Jones <jim.jones@uni-muenster.de>
Cc: Peter Smith <smithpb2250@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org, Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Subject: Re: [PATCH] Add pretty-printed XML output option
Date: Wed, 15 Feb 2023 12:11:22 +0100
Message-ID: <20230215111122.ogtc7iz4xuljufsv@alvherre.pgsql> (raw)
In-Reply-To: <10da4d21-8cc9-c8f7-2a6e-2fc90aff764b@uni-muenster.de>
On 2023-Feb-15, Jim Jones wrote:
> Hi Álvaro,
>
> As my test cases were not specifically about how the error message looks
> like, I thought that suppressing part of the error messages by setting
> VERBOSITY terse would suffice.[1] Is this approach not recommended?
Well, I don't see why we would depart from what we've been doing in the
rest of the XML tests. I did see that patch and I thought it was taking
the wrong approach.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Aprender sin pensar es inútil; pensar sin aprender, peligroso" (Confucio)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alvherre@alvh.no-ip.org, jim.jones@uni-muenster.de, smithpb2250@gmail.com, tgl@sss.pgh.pa.us, peter.eisentraut@enterprisedb.com
Subject: Re: [PATCH] Add pretty-printed XML output option
In-Reply-To: <20230215111122.ogtc7iz4xuljufsv@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox