From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Voillequin, Jean-Marc" <Jean-Marc.Voillequin@moodys.com>
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: xpath insert unexpected newlines
In-reply-to: <8718.1555683683@sss.pgh.pa.us>
References: 
 <1EC8157EB499BF459A516ADCF135ADCE3A23A9CA@LON-WGMSX712.ad.moodys.net>
 <8718.1555683683@sss.pgh.pa.us>
Comments: In-reply-to Tom Lane <tgl@sss.pgh.pa.us>
	message dated "Fri, 19 Apr 2019 10:21:23 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <23855.1555962518.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 22 Apr 2019 15:48:38 -0400
Message-ID: <23856.1555962518@sss.pgh.pa.us>
Precedence: bulk

I wrote:
> [ redirecting to pgsql-bugs ]
> "Voillequin, Jean-Marc" <Jean-Marc.Voillequin@moodys.com> writes:
>> It seems that xpath function add unexpected newlines in the xml element=
s it returns as array:

> I tried this:
> -           bytes =3D xmlNodeDump(buf, NULL, cur_copy, 0, 1);
> +           bytes =3D xmlNodeDump(buf, NULL, cur_copy, 0, 0);
> and that makes the discrepancy go away (both results are printed without
> any added whitespace).

> Thoughts?

[ crickets ]

Hearing nothing, I propose to change this in HEAD but not back-patch.
It still seems like a bug, but given the lack of previous complaints,
I'm not sure we'd get plaudits for changing this behavior in back
branches.

			regards, tom lane