From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Odd Shortcut behaviour in PG14 |
Date: | 2023-11-23 19:45:23 |
Message-ID: | 3170786.1700768723@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ron Johnson <ronljohnsonjr(at)gmail(dot)com> writes:
> Out of curiosity, what is the point of adding the "true" predicate no
> matter the position? Maybe I've created an incorrect truth table, but
> "true AND" (and "AND true") don't make any logical difference when added
> to (ekey > 0)*.*
Not only does it not make any logical difference, but it shouldn't
make any practical difference either, because the useless "true"
subclause will be thrown away very early in planning, before any
decisions would be taken on the strength of what is in the ON clause.
So I was skeptical that the details presented were even correct.
I think whatever is causing the behavioral change is something else
that the OP hasn't identified/controlled for. Hard to tell with
such fragmentary details.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2023-11-23 20:43:02 | Re: IPV6 issue |
Previous Message | Andreas Kretschmer | 2023-11-23 19:35:30 | Re: IPV6 issue |