Re: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
Richard Guo <guofenglinux@gmail.com>
From: Richard Guo <guofenglinux@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Lori Corbani <Lori.Corbani@jax.org>,
Thomas Munro <thomas.munro@gmail.com>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2025-10-30T03:24:49Z
Lists: pgsql-bugs
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Disable parallel plans for RIGHT_SEMI joins
- ef6168bafe9b 18.1 landed
- 257ee78341f2 19 (unreleased) landed
On Thu, Oct 30, 2025 at 1:00 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > Richard Guo <guofenglinux@gmail.com> writes: > > After spending a bit more time experimenting, I couldn't find a better > > query that shows a large difference between the costs of the PRSJ plan > > and the patched version plan. So I've updated the test case to use > > the aforementioned one. I also removed the reset statements and > > switched to the begin/rollback pattern for the test case. > v2 patch LGTM. Thanks for the review. I've pushed v2 and backpatched it to v18. Thanks to Lori for the report. - Richard