On Mon, Aug 14, 2017 at 7:36 PM, Michael Paquier
wrote:
> Thanks for adding the details directly, downgrading the hard way is
> what I am doing now using the past packages of libxml2 in Arch's
> archives [1]. ArchLinux is a bit wrong in the fact of shipping a
> package with a behavior change. Let'
On Mon, Aug 14, 2017 at 6:46 PM, Aleksander Alekseev
wrote:
> Hi Michael,
>
>> It's been one month since I have done some serious development with
>> Archlinux (I was abroad and away from the laptop dedicated to that),
>> and surprise, I can see failures in the PG regression tests, like the
>> fol
Hi Michael,
> I can confirm that I see the same errors on Arch Linux with latest
> updates when PostgreSQL is compiled with --with-libxml and/or
> --with-libxslt. I submitted a few details on bugs.archlinux.org [1]
> since probably not all Arch Linux maintainers know how to reproduce an
> issue.
>
Hi Michael,
> It's been one month since I have done some serious development with
> Archlinux (I was abroad and away from the laptop dedicated to that),
> and surprise, I can see failures in the PG regression tests, like the
> following short extract (result compared to expected/xml.out):
I can c
Hello,
On Sat, Aug 12, 2017 at 08:46:38PM +0900, Michael Paquier wrote:
> I can notice as well that no buildfarm machines are running ArchLinux
> now, so that's one reason why this got undetected until now. My own
> machines running Archlinux ARM have been unplugged for a full month,
> and I can s
On Sat, Aug 12, 2017 at 8:46 PM, Michael Paquier
wrote:
> I have not investigated much this problem yet, but has somebody else
> seen those diffs?
Coming back to that... Downgrading down to 2.9.4+4+g3169602-1 is
proving to put things back the way they should. Even downgrading to
2.9.4+91+g872fea9
Hi all,
It's been one month since I have done some serious development with
Archlinux (I was abroad and away from the laptop dedicated to that),
and surprise, I can see failures in the PG regression tests, like the
following short extract (result compared to expected/xml.out):
SELECT xmlparse(do