From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Heath Lord <heath.lord@crunchydata.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: REL_13_STABLE Windows 10 Regression Failures
Date: Tue, 10 Nov 2020 17:32:09 -0800
Message-ID: <20201111013209.ofirlzauhexoe4uj@alap3.anarazel.de> (raw)
In-Reply-To: <1987800.1604942314@sss.pgh.pa.us>
References: <20201109171446.GA32555@alvherre.pgsql>
<1987800.1604942314@sss.pgh.pa.us>
High,
On 2020-11-09 12:18:34 -0500, Tom Lane wrote:
> Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> > Hmm, line 202 is the ereport in this test:
>
> > if (!IsA(expr, ColumnRef))
> > ereport(ERROR,
> > (errcode(ERRCODE_FEATURE_NOT_SUPPORTED),
> > errmsg("only simple column references are allowed in CREATE STATISTICS")));
>
> > Not sure why that gives rise to the upper parts of the stack there.
>
> Yeah, it seems like the error-recovery longjmp has suddenly broken;
> but why here? There's nothing unusual about this specific error case.
Perhaps PG_exception_stack got corrupted somehow? An oversized write to
a neighboring var?
Not sure if that works on mingw, but building with address sanitizer /
asan might be informative.
Greetings,
Andres Freund
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-bugs@postgresql.org
Cc: andres@anarazel.de, tgl@sss.pgh.pa.us, alvherre@alvh.no-ip.org, heath.lord@crunchydata.com, pgsql-bugs@lists.postgresql.org
Subject: Re: REL_13_STABLE Windows 10 Regression Failures
In-Reply-To: <20201111013209.ofirlzauhexoe4uj@alap3.anarazel.de>
* 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