| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Query generates infinite loop |
| Date: | 2022-05-04 19:24:21 |
| Message-ID: | 2459340.1651692261@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Jeff Janes <jeff(dot)janes(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2022-05-05 12:10:19 | BUG #17474: Segmentation fault from INSERT ( JumbleExpr ) |
| Previous Message | Jeff Janes | 2022-05-04 19:01:27 | Re: Query generates infinite loop |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-05-04 19:27:21 | Re: Atomic GetFreeIndexPage()? |
| Previous Message | Chris Cleveland | 2022-05-04 19:16:02 | Atomic GetFreeIndexPage()? |