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 1nmKbr-0005nN-4x for pgsql-hackers@arkaria.postgresql.org; Wed, 04 May 2022 19:24:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nmKbp-0002WL-SD for pgsql-hackers@arkaria.postgresql.org; Wed, 04 May 2022 19:24:25 +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 1nmKbp-0002WC-J3 for pgsql-hackers@lists.postgresql.org; Wed, 04 May 2022 19:24:25 +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 1nmKbn-0006ib-CK for pgsql-hackers@lists.postgresql.org; Wed, 04 May 2022 19:24:24 +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 244JOLsq2459341; Wed, 4 May 2022 15:24:21 -0400 From: Tom Lane To: Jeff Janes cc: PostgreSQL Hackers Subject: Re: Query generates infinite loop In-reply-to: References: <91B44E7B-68D5-448F-95C8-B4B3B0F5DEAF@duckdblabs.com> <2842828.1650474225@sss.pgh.pa.us> <3010353.1650490989@sss.pgh.pa.us> Comments: In-reply-to Jeff Janes message dated "Wed, 04 May 2022 15:01:27 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2459339.1651692261.1@sss.pgh.pa.us> Date: Wed, 04 May 2022 15:24:21 -0400 Message-ID: <2459340.1651692261@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Jeff Janes writes: > The regression test you added for this change causes an infinite loop when > run against an unpatched server with --install-check. That is a bit > unpleasant. Is there something we can and should do about that? I was > expecting regression test failures of course but not an infinite loop > leading towards disk exhaustion. We very often add regression test cases that will cause unpleasant failures on unpatched code. I categorically reject the idea that that's not a good thing, and question why you think that running known-broken code against a regression suite is an important use case. regards, tom lane