Re: xmlserialize bug - extra empty row at the end - Mailing list pgsql-hackers

From Tom Lane
Subject Re: xmlserialize bug - extra empty row at the end
Date
Msg-id 3837658.1682261289@sss.pgh.pa.us
Whole thread Raw
In response to Re: xmlserialize bug - extra empty row at the end  (Jim Jones <jim.jones@uni-muenster.de>)
Responses Re: xmlserialize bug - extra empty row at the end  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
Jim Jones <jim.jones@uni-muenster.de> writes:
> On 23.04.23 07:31, Pavel Stehule wrote:
>> Looks so there is an extra empty row.

> Good catch! It looks like it comes directly from libxml2.

Is it really a bug?  If libxml2 itself is putting in that newline,
I'm not sure we should take it on ourselves to strip it.

> I'll do some digging to see if there is a good way to get rid of this 
> newline or if we need to chose a different dump function.

If we do want to strip it, I'd just add a couple lines of code
to delete any trailing newlines at the end of the process.
Compare, eg, pchomp().

            regards, tom lane



pgsql-hackers by date:

Previous
From: Isaac Morland
Date:
Subject: Re: xmlserialize bug - extra empty row at the end
Next
From: Pavel Stehule
Date:
Subject: Re: xmlserialize bug - extra empty row at the end