| From: | MESZAROS Attila <tilla(at)chiara(dot)csoma(dot)elte(dot)hu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Patrick Giagnocavo <a222(at)redrose(dot)net>, pgsql-sql(at)postgreSQL(dot)org |
| Subject: | Re: [SQL] qurey plan and indices |
| Date: | 1999-08-05 14:59:41 |
| Message-ID: | Pine.LNX.3.96.990805165414.26220B-100000@chiara.csoma.elte.hu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
> However, the *real* problem here is that the inner query is treated
> as a subplan, which means it is re-evaluated for each tuple scanned
> by the outer query. This is not very bright; the system ought to
> notice that the inner query does not depend on the state of the
> outer query, and do it only once. There is already a notion of
> InitPlan vs. SubPlan. I'm not sure why this case is being classified
> as a SubPlan, but it sure looks like it ought to be done as an
> InitPlan...
So this means, it is a bug somewhere in the planner?
who should we report this??
Attila
any workarounds?
[better than temptables?]
| From | Date | Subject | |
|---|---|---|---|
| Next Message | rob caSSon | 1999-08-05 15:24:25 | Re: [SQL] primary key view failure |
| Previous Message | MESZAROS Attila | 1999-08-05 14:51:21 | Re: [SQL] qurey plan and indices |