| From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
|---|---|
| To: | Andrei Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru> |
| Cc: | Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, zuming(dot)jiang(at)inf(dot)ethz(dot)ch, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18261: Inconsistent results of SELECT affected by joined subqueries |
| Date: | 2024-01-08 11:50:56 |
| Message-ID: | CAMbWs49igjcszLgicb4D1N21_5iNDoxheJ7KFmAcs_z=Lx6jhg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Jan 5, 2024 at 11:32 AM Andrei Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru>
wrote:
> The regression test shows where two fully equal join clauses, applied on
> different join levels, differ by the only required_relids. It covers the
> problem and can be helpful by itself. IMO, one line in this test is
> redundant (see attachment).
Hmm, I don't think the insert statement in the test case is redundant.
It's needed to verify that the query in the test case gives the correct
result. Without the insert statement, the wrong plan would give the
same result as the correct plan, i.e., an empty set in this case.
IMO, if we make some code changes and add a test case for that, we need
to ensure the test can give a different (and correct of course) result
than what came before.
Thanks
Richard
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Devrim Gündüz | 2024-01-08 12:29:01 | Re: centos7 setup - repomd.xml signature could not be verified for pgdg-common |
| Previous Message | Kieren Diment | 2024-01-08 08:40:34 | centos7 setup - repomd.xml signature could not be verified for pgdg-common |