pg.ddx.io pgsql-hackers@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jim Jones <jim.jones@uni-muenster.de>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Peter Smith <smithpb2250@gmail.com>
Cc: Nikolay Samokhvalov <samokhvalov@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Andrey Borodin <amborodin86@gmail.com>
Subject: Re: [PATCH] Add pretty-printed XML output option
Date: Thu, 09 Mar 2023 12:38:07 -0500
Message-ID: <429187.1678383487@sss.pgh.pa.us> (raw )
In-Reply-To: <1cbe1087-6acb-2b0a-dc9b-0a2d5b99e466@uni-muenster.de >
References: <2f5df461-dad8-6d7d-4568-08e10608a69b@uni-muenster.de >
<62643598-b80d-90f4-8901-b85dccadf4c4@enterprisedb.com >
<CANNMO+Kwb4_87G8qDeN+Vk1B1vX3HvgoGW+13fJ-b6rj7qbAww@mail.gmail.com >
<beb5a47d-4684-4b2f-8647-bacb6bd60acf@uni-muenster.de >
<CANNMO+L5X2ynyXL2RK7gTVA-pj=Z8o8FCCr6RwLfRK_LinjSbg@mail.gmail.com >
<d79950fd-b3f5-783c-919a-a95de23c0c2c@enterprisedb.com >
<4c2efca5-8257-2424-6687-07c65e319e95@uni-muenster.de >
<CAHut+PtMHeBBZ2zv0Bk7-4KMkSrrxZ9PZxUCzhpwTGVk+8G3cw@mail.gmail.com >
<2eac4d78-2b20-e8ec-54cc-22a88653a1cc@uni-muenster.de >
<CAHut+PsgXxbzzsG+VqHUa4Kz3G4B-anNmF3-GENwuUdfMJtowA@mail.gmail.com >
<fb2a543b-e615-d9ba-8402-909631f9b212@uni-muenster.de >
<CAHut+Pvryt_+wA7TwKVaaF0e6Pm5LaPZQLKatp=78oFd8vMh3A@mail.gmail.com >
<6cb296fe-4b49-3691-633e-2e2366997b04@uni-muenster.de >
<3baf8f25-3bd7-7db5-0b31-e4c92b6269ba@enterprisedb.com >
<1cbe1087-6acb-2b0a-dc9b-0a2d5b99e466@uni-muenster.de >
While reviewing this patch, I started to wonder why we don't eliminate
the maintenance hassle of xml_1.out by putting in a short-circuit
at the top of the test, similar to those in some other scripts:
/* skip test if XML support not compiled in */
SELECT '<value>one</value>'::xml;
\if :ERROR
\quit
\endif
(and I guess xmlmap.sql could get the same treatment).
The only argument I can think of against it is that the current
approach ensures we produce a clean error (and not, say, a crash)
for all xml.c entry points not just xml_in. I'm not sure how much
that's worth though. The compiler/linker would tell us if we miss
compiling out every reference to libxml2.
Thoughts?
regards, tom lane
view thread (70+ messages) latest in thread
Message-ID: <429187.1678383487@sss.pgh.pa.us>
Permalink: ../429187.1678383487@sss.pgh.pa.us/
Also on: postgresql.org/message-id/429187.1678383487@sss.pgh.pa.us
copy link · copy postgr.es
reply 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: tgl@sss.pgh.pa.us, jim.jones@uni-muenster.de, peter.eisentraut@enterprisedb.com, smithpb2250@gmail.com, samokhvalov@gmail.com, pgsql-hackers@lists.postgresql.org, amborodin86@gmail.com
Subject: Re: [PATCH] Add pretty-printed XML output option
In-Reply-To: <429187.1678383487@sss.pgh.pa.us>
* 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