From: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andrey Borodin <amborodin86(at)gmail(dot)com> |
Subject: | Re: [PATCH] Add pretty-printed XML output option |
Date: | 2023-03-09 18:41:29 |
Message-ID: | 4b1e081b-831a-e539-9864-8d8a16a66669@uni-muenster.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 09.03.23 18:38, Tom Lane wrote:
> 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
Hi Tom,
I agree it would make things easier and it could indeed save some time
(and some CI runs ;)).
However, checking in the absence of libxml2 if an error message is
raised, and checking if this error message is the one we expect, is IMHO
also a very nice test. But I guess I could also live with skipping the
whole thing.
Best, Jim
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2023-03-09 18:51:09 | WaitEventSet resource leakage |
Previous Message | Alvaro Herrera | 2023-03-09 18:36:47 | Re: Doc: Rework contrib appendix -- informative titles, tweaked sentences |