Re: Assert failure of the cross-check for nullingrels
Richard Guo <guofenglinux@gmail.com>
From: Richard Guo <guofenglinux@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2023-06-07T02:25:40Z
Lists: pgsql-hackers
On Wed, Jun 7, 2023 at 4:22 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > Alvaro Herrera <alvherre@alvh.no-ip.org> writes: > > So, is this done? I see that you made other commits fixing related code > > several days after this email, but none seems to match the changes you > > posted in this patch; and also it's not clear to me that there's any > > test case where this patch is expected to change behavior. (So there's > > also a question of whether this is a bug fix or rather some icying on > > cake.) This issue is fixed at 991a3df22. > Well, the bugs I was aware of ahead of PGCon are all fixed, but there > are some new reports I still have to deal with. I left the existing > open issue open, but maybe it'd be better to close it and start a new > one? I went ahead and closed it, and then started two new open items for the two new issues --- one is about assert failure and wrong query results due to incorrectly removing PHVs, the other is about inconsistent nulling bitmap in nestloop parameters. Thanks Richard
Commits
-
In clause_is_computable_at(), test required_relids for clone clauses.
- b9c755a2f625 16.0 landed
-
Tweak API of new function clause_is_computable_at().
- 8a2523ff3540 16.0 landed