Skip site navigation (1) Skip section navigation (2)

Re: RangeTblEntry modifications

From: Alex Pilosov <alex(at)pilosoft(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: RangeTblEntry modifications
Date: 2001-07-01 00:01:54
Message-ID: Pine.BSO.4.10.10106301959350.7004-100000@spider.pilosoft.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Sat, 30 Jun 2001, Tom Lane wrote:

> I'm not sure I buy this, however.  You'll need an actual
> RTE-as-function-call variant that has the function OID and compiled list
> of arguments.  Remember that the parsetree may live a lot longer than
> any specific Portal.  For a function call, we'll need to build the
> Portal from the function-call-describing RTE at the start of execution,
> not during parsing.

I think I just understood what you were saying: having tupleDesc in RTE is
not kosher, because RTE can last longer than a given tupleDesc?

So, essentially I will need to extract attnames/atttypes from TupleDesc
and store them separately...

Or I'm totally off my rocker?


In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2001-07-01 04:47:41
Subject: Re: RangeTblEntry modifications
Previous:From: Peter EisentrautDate: 2001-06-30 23:50:08
Subject: FE/BE protocol oddity

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group