Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kcAoU-0007wZ-AT for pgsql-bugs@arkaria.postgresql.org; Mon, 09 Nov 2020 17:18:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kcAoT-0000Rr-6n for pgsql-bugs@arkaria.postgresql.org; Mon, 09 Nov 2020 17:18:41 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kcAoT-0000Rk-0Y for pgsql-bugs@lists.postgresql.org; Mon, 09 Nov 2020 17:18:41 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kcAoQ-0006jN-Mi for pgsql-bugs@lists.postgresql.org; Mon, 09 Nov 2020 17:18:40 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 0A9HIYm61987801; Mon, 9 Nov 2020 12:18:35 -0500 From: Tom Lane To: Alvaro Herrera cc: Heath Lord , pgsql-bugs@lists.postgresql.org Subject: Re: REL_13_STABLE Windows 10 Regression Failures In-reply-to: <20201109171446.GA32555@alvherre.pgsql> References: <20201109171446.GA32555@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Mon, 09 Nov 2020 14:14:46 -0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1987799.1604942314.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 09 Nov 2020 12:18:34 -0500 Message-ID: <1987800.1604942314@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Alvaro Herrera 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 i= n 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