From: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Richard Guo <guofenglinux(at)gmail(dot)com>, Benoit Ryder <b(dot)ryder(at)ateme(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #18429: Inconsistent results on similar queries with join lateral |
Date: | 2024-05-10 02:06:25 |
Message-ID: | CADkLM=fbcjMvDrYHjstLh1CiwGJft7q9MCqmTnTsg1_NmT20eA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
>
> I didn't add such a test because there are already several cases
> (in foreign_data.sql, IIRC) that trigger the assert, which is
> how come I found the problem in the first place. Admittedly,
> those depend on potentially-changeable details of an
> information_schema view, so maybe it'd be better to have a
> bespoke test.
>
I recently had a situation where having a bespoke test would have been
helpful. Attached is a mostly-verbatim formalization of the tests from the
original email. Q3 was of particular use to me.
Attachment | Content-Type | Size |
---|---|---|
v1-0001-Regression-tests-for-BUG-18429.patch | text/x-patch | 4.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Shlok Kyal | 2024-05-10 06:05:09 | Re: BUG #18433: Logical replication timeout |
Previous Message | Melanie Plageman | 2024-05-09 21:56:34 | Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae |