From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Assert failure of the cross-check for nullingrels |
Date: | 2023-06-07 02:25:40 |
Message-ID: | CAMbWs48mnX6bqHPQMsjahfjgNB+DzOiuMA_xMwXiODte2TNzdw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jun 7, 2023 at 4:22 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2023-06-07 02:48:37 | Re: Improve join_search_one_level readibilty (one line change) |
Previous Message | 蔡梦娟 (玊于) | 2023-06-07 02:25:25 | 回复:回复:Fix missing initialization of delayChkptEnd |