From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> |
Cc: | Richard Guo <guofenglinux(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: havingQual vs hasHavingQual buglets |
Date: | 2022-10-18 14:46:46 |
Message-ID: | 2647067.1666104406@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> writes:
> On Tue, Oct 18, 2022 at 9:47 AM Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
>> On Tue, Oct 18, 2022 at 5:37 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> I came across a couple of places in the planner that are checking
>>> for nonempty havingQual; but since these bits run after
>>> const-simplification of the HAVING clause, that produces the wrong
>>> answer for a constant-true HAVING clause (which'll be folded to
>>> empty). Correct code is to check root->hasHavingQual instead.
> The postgres_fdw bits would be my oversight. :-(
No worries --- I think the one in set_subquery_pathlist is probably
my fault :-(
> +1 HEAD only seems reasonable.
Pushed that way; thanks for looking.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2022-10-18 14:55:03 | Re: hash_xlog_split_allocate_page: failed to acquire cleanup lock |
Previous Message | Fabrice Chapuis | 2022-10-18 14:35:02 | Re: Logical replication timeout problem |