| From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: TupleDescs and refcounts and such, again |
| Date: | 2006-12-27 23:12:43 |
| Message-ID: | 1167261163.3633.64.camel@silverbirch.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2006-12-27 at 18:05 -0500, Tom Lane wrote:
> "Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> > Is it possible to allocate the subquery in a child context of the main
> > query, so that it is technically a different context, yet can be freed
> > simultaneously?
>
> That's exactly what the code *was* doing, but the problem is that we'd
> free the child context during ExecEndSubqueryScan, at which point the
> tupdesc is still needed.
OK, I guess my only other question is to do with recursive/hierarchical
queries: How will we handle those? All in same context?
I guess many subqueries are transformable into main joins anyway, so the
distinction is probably moot anyhow.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-12-27 23:17:38 | Re: pg_hba.conf hostname todo |
| Previous Message | Tom Lane | 2006-12-27 23:07:25 | Re: Per-database search_path |