| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Christopher Kings-Lynne <chris(dot)kings-lynne(at)calorieking(dot)com>, "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Bernd Helmle <mailings(at)oopsware(dot)de>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Susanne Ebrecht <susanne(dot)ebrecht(at)credativ(dot)de> |
| Subject: | Re: [PATCHES] 8.2 features? |
| Date: | 2006-07-21 03:09:47 |
| Message-ID: | 44C0457B.1010303@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers pgsql-patches |
Tom Lane wrote:
> No, I guess I confused you by talking about the executor representation
> at the same time. This is really unrelated to the executor. The join
> tree I'm thinking of here is the data structure that dangles off
> Query.jointree --- it's a representation of the query's FROM clause,
> and (at present) can contain RangeTblRef, FromExpr, and JoinExpr nodes.
> See the last hundred or so lines of primnodes.h for some details.
> The jointree is used by the planner to compute the plan node tree that
> the executor will run, but it's not the same thing.
Ah, that helps. Thanks for the explanation. I'll start digging in again...
Thanks,
Joe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-07-21 14:08:32 | Re: [PATCHES] 8.2 features? |
| Previous Message | Tom Lane | 2006-07-21 00:46:13 | Re: [PATCHES] 8.2 features? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-07-21 03:22:40 | Re: [PATCHES] modular pg_regress.sh |
| Previous Message | Gavin Sherry | 2006-07-21 01:05:40 | Re: Units in postgresql.conf |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-07-21 03:22:40 | Re: [PATCHES] modular pg_regress.sh |
| Previous Message | Tom Lane | 2006-07-21 00:46:13 | Re: [PATCHES] 8.2 features? |