From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
---|---|
To: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Inconsistent RestrictInfo serial numbers |
Date: | 2024-10-09 02:14:58 |
Message-ID: | CAMbWs49Z1f+v1VhM=Nx10RTfR6s5wxQm=i8VB40r84M3iOFZYw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Oct 8, 2024 at 9:02 PM Ashutosh Bapat
<ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> wrote:
> But I don't see any relation specific information being
> considered while deciding whether the clause is constant false.
Isn't rel->notnullattnums relation specific information? We need this
information to decide if a Var cannot be NULL.
> So may
> be we should do this processing elsewhere and replace the original
> clause itself?
I’m not sure about this. Different versions of the same qual clause
can lead to different conclusions about whether it can be reduced to
constant-FALSE. I don't think it is possible to replace the original
clause; we need to do this processing on a version-by-version basis.
Thanks
Richard
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Bossart | 2024-10-09 02:36:03 | Re: Popcount optimization using AVX512 |
Previous Message | Shinya Kato | 2024-10-09 02:10:37 | Set AUTOCOMMIT to on in script output by pg_dump |