Re: Lack of T_TargetEntry in exprType function

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Lack of T_TargetEntry in exprType function
Date: 2018-03-20 14:43:08
Message-ID: 12279.1521556988@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru> writes:
> On 20.03.2018 17:00, Tom Lane wrote:
>> It's intentional because that's not considered an executable
>> expression.

> I tried to apply this function to the argument of Aggref and it has
> exactly this kind.
> Aggref is executable expression. This is why I thought that all its
> arguments also should be considered as executable expressions, shouldn't
> they?

Not really. They're a list of executable expressions, which is not the
same thing --- in particular, exprType() on the whole list wouldn't give a
useful result. The TargetEntrys are best thought of as part of the list
superstructure.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeevan Chalke 2018-03-20 14:46:29 Re: [HACKERS] Partition-wise aggregation/grouping
Previous Message Masahiko Sawada 2018-03-20 14:41:57 Re: XID-assigned idle transactions affect vacuum's job.