Re: Increase value of OUTER_VAR

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Andrey Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, Amit Langote <amitlangote09(at)gmail(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Increase value of OUTER_VAR
Date: 2021-04-07 13:35:56
Message-ID: 97563e37-3011-67d7-e816-e7f899311c54@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 06.03.21 15:59, Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> writes:
>> On 04.03.21 20:01, Tom Lane wrote:
>>> (2) Does that datatype change need to propagate anywhere besides
>>> what I touched here? I did not make any effort to search for
>>> other places.
>
>> I think
>
>> Var.varnosyn
>> CurrentOfExpr.cvarno
>
>> should also have their type changed.
>
> Agreed as to CurrentOfExpr.cvarno. But I think the entire point of
> varnosyn is that it saves the original rangetable reference and
> *doesn't* get overwritten with OUTER_VAR etc. So that one is a
> different animal, and I'm inclined to leave it as Index.

Can we move forward with this?

I suppose there was still some uncertainty about whether all the places
that need changing have been identified, but do we have a better idea
how to find them?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-04-07 13:40:37 Re: Increase value of OUTER_VAR
Previous Message Peter Eisentraut 2021-04-07 13:32:55 Re: SSL SNI