| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Martijn van Oosterhout" <kleptog(at)svana(dot)org> |
| Cc: | "Zoltan Boszormenyi" <zb(at)cybertec(dot)at>, "Tatsuo Ishii" <ishii(at)postgresql(dot)org>, "David Fetter" <david(at)fetter(dot)org>, "PG Hackers" <pgsql-hackers(at)postgresql(dot)org>, <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] WITH RECURSIVE patch V0.1 |
| Date: | 2008-05-19 14:22:10 |
| Message-ID: | 87ej7ype5p.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
"Martijn van Oosterhout" <kleptog(at)svana(dot)org> writes:
> From an implementation point of view, the only difference between
> breadth-first and depth-first is that your tuplestore needs to be LIFO
> instead of FIFO.
I think it's not so simple. How do you reconcile that concept with the join
plans like merge join or hash join which expect you to be able to be able to
process the records in a specific order?
It sounds like you might have to keep around a stack of started executor nodes
or something but hopefully we can avoid anything like that because, well, ick.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2008-05-19 15:01:52 | Re: triggers on prepare, commit, rollback... ? |
| Previous Message | Tom Lane | 2008-05-19 14:10:38 | Re: triggers on prepare, commit, rollback... ? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2008-05-19 17:48:27 | Re: Patch to change psql default banner v6 |
| Previous Message | Hannu Krosing | 2008-05-19 13:51:47 | Re: WITH RECURSIVE patch V0.1 |