Re: Increase value of OUTER_VAR - Mailing list pgsql-hackers

From Andrey Lepikhov
Subject Re: Increase value of OUTER_VAR
Date
Msg-id e7dc09bc-0a2b-860d-107c-3f3345040154@postgrespro.ru
Whole thread Raw
In response to Re: Increase value of OUTER_VAR  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Increase value of OUTER_VAR  (Aleksander Alekseev <aleksander@timescale.com>)
Re: Increase value of OUTER_VAR  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2/7/21 21:23, Tom Lane wrote:
> So I'm inclined to propose pushing this and seeing what happens.

+1
But why the Index type still uses for indexing of range table entries?
For example:
- we give int resultRelation value to create_modifytable_path() as Index 
nominalRelation value.
- exec_rt_fetch(Index) calls list_nth(int).
- generate_subquery_vars() accepts an 'Index varno' value

It looks sloppy. Do you plan to change this in the next commits?

-- 
regards,
Andrey Lepikhov
Postgres Professional



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Diagnostic comment in LogicalIncreaseXminForSlot
Next
From: David Rowley
Date:
Subject: Re: [PATCH] expand the units that pg_size_pretty supports on output