Re: REL_13_STABLE Windows 10 Regression Failures

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Heath Lord <heath(dot)lord(at)crunchydata(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: REL_13_STABLE Windows 10 Regression Failures
Date: 2020-11-09 17:18:34
Message-ID: 1987800.1604942314@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Vik Fearing 2020-11-09 19:45:13 Re: BUG #16706: insert into on conflict(pk) do update error violates not-null constraint
Previous Message Alvaro Herrera 2020-11-09 17:14:46 Re: REL_13_STABLE Windows 10 Regression Failures