Re: Inconsistent RestrictInfo serial numbers
Richard Guo <guofenglinux@gmail.com>
From: Richard Guo <guofenglinux@gmail.com>
To: Andrei Lepikhov <lepihov@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2024-10-09T06:06:11Z
Lists: pgsql-hackers
On Wed, Oct 9, 2024 at 11:15 AM Andrei Lepikhov <lepihov@gmail.com> wrote: > On 10/8/24 18:20, Richard Guo wrote: > > To fix, I think we can reset the root->last_rinfo_serial counter after > > generating the additional constant-FALSE RestrictInfo. Please see > > attached. > The approach will work, no doubt. But why are you using such a wordy > approach with save_last_rinfo_serial? I'd say it is better to invent a > function like make_rinfo_variant() or something like that and explicitly > set rinfo_serial. It will be easier to read and understand in the > future, won't it? Maybe, but I don't think it's worth creating a new function for such a straightforward operation, nor do I think it's worth changing the internals of make_restrictinfo() regarding how root->last_rinfo_serial is incremented, as that would require updating all the callers of this function. 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