Re: Inconsistent RestrictInfo serial numbers
Richard Guo <guofenglinux@gmail.com>
From: Richard Guo <guofenglinux@gmail.com>
To: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2024-10-09T02:14:58Z
Lists: pgsql-hackers
On Tue, Oct 8, 2024 at 9:02 PM Ashutosh Bapat <ashutosh.bapat.oss@gmail.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
Commits
-
Fix inconsistent RestrictInfo serial numbers
- 78b1c553bb1c 17.1 landed
- f00ab1fd156e 18.0 landed
-
Recalculate where-needed data accurately after a join removal.
- a3179ab692be 18.0 cited
-
Add better handling of redundant IS [NOT] NULL quals
- b262ad440ede 17.0 cited