From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: pgsql-committers@lists.postgresql.org, Andrew Dunstan <andrew@dunslane.net>
Subject: Re: pgsql: Emit parameter values during query bind/execute errors
Date: Thu, 12 Dec 2019 12:41:26 -0500
Message-ID: <2001.1576172486@sss.pgh.pa.us> (raw)
In-Reply-To: <20191212164720.GA27169@alvherre.pgsql>
References: <20191212164720.GA27169@alvherre.pgsql>
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> Hmm, the affected ones (jacana and fairywren only AFAICS) seem to be
> gcc-based, which presumably work differently than the msvc-based in how
> newlines are interpreted in the test script. I pushed an attempted
> blind fix.
> I *hope* that those two are not the only Windows ones running the
> pgbench tap test!
[ scrapes buildfarm results... ] The Windows critters that are
running that test seem to be
name | operating_system | compiler
-----------+------------------+---------------
bowerbird | Windows | Visual Studio
drongo | Windows | Visual Studio
fairywren | Windows / Msys | gcc
jacana | Windows | gcc
So yeah, the MSVC ones were happy with the test as you had it.
Interesting ... it's not obvious why that would have anything
to do with the behavior of a Perl regexp. Maybe they are using
a different Perl version?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, alvherre@2ndquadrant.com, andrew@dunslane.net
Subject: Re: pgsql: Emit parameter values during query bind/execute errors
In-Reply-To: <2001.1576172486@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox