Re: BUG #19710: Incorrect DELETE result after LEFT JOIN optimization

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>
Cc: 2320415112(at)qq(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19710: Incorrect DELETE result after LEFT JOIN optimization
Date: 2026-09-21 13:49:42
Message-ID: 635522.1789998582@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com> writes:
> On Mon, 21 Sept 2026 at 12:05, PG Bug reporting form <noreply(at)postgresql(dot)org>
> wrote:
>> On PostgreSQL 17.10, a `DELETE` statement containing an `EXISTS` subquery
>> with two `LEFT JOIN`s deletes a row even though the subquery predicate is
>> false.

> AFAICS this has been fixed[1] and will be part of next minor versions.

Yeah, this example is pretty nearly a duplicate of bug #19560 [1],
which prompted that rewrite.

regards, tom lane

[1] https://www.postgresql.org/message-id/19560-54cd7ede78d5e355%40postgresql.org

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Manuel Reyes Bravo 2026-09-21 16:17:13 Re: Detaching a child table makes an expression using it unrestorable
Previous Message Andrey Borodin 2026-09-21 10:17:40 Re: BUG #19698: IMPORT FOREIGN SCHEMA treats a NOT VALID NOT NULL constraint as validated