Re: REL_13_STABLE Windows 10 Regression Failures

Andres Freund <andres@anarazel.de>

From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, Heath Lord <heath.lord@crunchydata.com>, pgsql-bugs@lists.postgresql.org
Date: 2020-11-11T01:32:09Z
Lists: pgsql-bugs
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



Commits

  1. Work around issues in MinGW-64's setjmp/longjmp support.

  2. Remove large fill factor support from dynahash.c.

  3. Use the properly transformed RangeVar for expandTableLikeClause().