| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: TopPlan, again |
| Date: | 2007-02-19 03:47:35 |
| Message-ID: | 87lkiuq04o.fsf@stark.xeocode.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Comments, objections? Also, any thoughts about the names to use for
> these new node types? As I commented last year, I'm not completely
> happy with "TopPlan" because it won't actually be a subtype of Plan,
> but I don't have a better idea. Also I'm unsure what to call the
> cut-down RangeTblEntry struct; maybe RunTimeRangeTblEntry?
My only though is that I suspect this will somehow relate to the cte stuff I
was doing for recursive queries. I'm not exactly clear how yet though.
I think this has more to do with the RangeTable stuff than the TopPlan though.
I was probably going to need a new kind of RangeTable representing a Subquery
that was a reference to a cte rather than a separate subquery.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleg Bartunov | 2007-02-19 04:47:03 | Re: n-gram search function |
| Previous Message | Tom Lane | 2007-02-19 03:28:49 | Re: TopPlan, again |