Re: UNION ALL - Var attno

From: sri harsha <sriharsha9992(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: UNION ALL - Var attno
Date: 2016-04-29 05:42:40
Message-ID: CAP6OGLHr_EqLaP-PtfuJxBLPOPqVfXqW+TV_-MyB7kjmfGU1_w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Its not an OpExpr . It is a VAR , got it from "reltargetlist" in base
relation ( RelOptInfo) . Can you shed some light on where the conversion
from 141 to "original" attribute number takes place ??

Regards,
Harsha

On Fri, Apr 29, 2016 at 10:03 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> sri harsha <sriharsha9992(at)gmail(dot)com> writes:
> > Assume the following query ,
> > (SELECT a * 1 , b FROM TABLE_1) UNION ALL (SELECT a *1 , b FROM TABLE_2);
>
> > In this query , attribute number of the VARs are 141 and 2 respectively
> !!
>
> I doubt it.
>
> Maybe you're looking at something that's not a Var, possibly an OpExpr,
> but assuming it's a Var? The fact that 141 is the pg_proc OID of int4mul
> lends considerable weight to this suspicion ...
>
> regards, tom lane
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas Seltenreich 2016-04-29 06:31:00 [sqlsmith] Failed assertion in BecomeLockGroupLeader
Previous Message Tom Lane 2016-04-29 04:39:32 Re: VS 2015 support in src/tools/msvc