From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff Janes <jeff.janes@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Query generates infinite loop
Date: Wed, 04 May 2022 15:24:21 -0400
Message-ID: <2459340.1651692261@sss.pgh.pa.us> (raw)
In-Reply-To: <CAMkU=1yp1S5cwj_e762D_tNHT5w=ZKDB3k6UCmSaTkbnddSwOA@mail.gmail.com>
References: <91B44E7B-68D5-448F-95C8-B4B3B0F5DEAF@duckdblabs.com>
<CAFj8pRDzVzTfsnxs_T9T7k=HW_gWCryo==rVB-AX4R6pXo85xQ@mail.gmail.com>
<2842828.1650474225@sss.pgh.pa.us>
<3010353.1650490989@sss.pgh.pa.us>
<CAMkU=1yp1S5cwj_e762D_tNHT5w=ZKDB3k6UCmSaTkbnddSwOA@mail.gmail.com>
Jeff Janes <jeff.janes@gmail.com> 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
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-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, jeff.janes@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: Query generates infinite loop
In-Reply-To: <2459340.1651692261@sss.pgh.pa.us>
* 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