Re: BUG #19059: PostgreSQL fails to evaluate the cheaper expression first, leading to 45X performance degradation

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: jinhui(dot)lai(at)qq(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19059: PostgreSQL fails to evaluate the cheaper expression first, leading to 45X performance degradation
Date: 2025-09-20 22:54:54
Message-ID: 84B5D601-C007-4B07-9ECB-CDD06E47B949@thebuild.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On Sep 20, 2025, at 14:19, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> While we've not gotten a huge amount of push-back about the top-level
> re-ordering, there's been some complaints. So I'm not eager to
> propagate the idea further down.

And tangentially, doesn't the SQL standard make it implementation-defined if OR short-circuits or not?

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2025-09-20 23:19:03 Re: BUG #19059: PostgreSQL fails to evaluate the cheaper expression first, leading to 45X performance degradation
Previous Message Tom Lane 2025-09-20 21:19:22 Re: BUG #19059: PostgreSQL fails to evaluate the cheaper expression first, leading to 45X performance degradation