Re: XMLSerialize: version and explicit XML declaration

From: solai v <solai(dot)cdac(at)gmail(dot)com>
To: Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: XMLSerialize: version and explicit XML declaration
Date: 2026-08-04 03:53:11
Message-ID: CAF0whuehdj8xrVLmcUs=5HYMx-SYDsV+8WxXXE+Cb9ApUSMAWw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Aug 3, 2026 at 7:40 PM Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> wrote:
>
> rebase

Hi Jim,

I tested the latest v9 patch on PostgreSQL 20devel.
The patch applied cleanly and the build completed successfully with
libxml support enabled. I also ran the regression tests, and all tests
passed.
I verified the new functionality introduced by the patch:
INCLUDING XMLDECLARATION correctly adds the XML declaration.
EXCLUDING XMLDECLARATION correctly removes the XML declaration.
VERSION '1.0' produces the expected output.
VERSION '1.1' generates the expected warning while still producing valid output.
An invalid version such as VERSION '2.0' correctly raises an error for
DOCUMENT values.
For CONTENT values, VERSION '2.0' is accepted as expected.
I also verified that the existing XMLSERIALIZE behavior remains
unchanged when the new options are not used.

From my testing, the patch works as expected, and I did not observe any issues.

Regards,
solai

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2026-08-04 04:11:33 Re: Fix NO_OOM handling in MemoryContextAllocAligned
Previous Message solai v 2026-08-04 03:50:59 Re: [SP-]GiST IOS visibility bug (was: Why doens't GiST require super-exclusive lock)