From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
---|---|
To: | david(at)fetter(dot)org |
Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-patches(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org, y-asaba(at)sraoss(dot)co(dot)jp |
Subject: | Re: [PATCHES] WITH RECUSIVE patches 0723 |
Date: | 2008-07-26 03:23:46 |
Message-ID: | 20080726.122346.51295854.t-ishii@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
> Thanks for the patch :)
>
> Now, I get a different problem, this time with the following code
> intended to materialize paths on the fly and summarize down to a
> certain depth in a tree:
>
> CREATE TABLE tree(
> id INTEGER PRIMARY KEY,
> parent_id INTEGER REFERENCES tree(id)
> );
>
> INSERT INTO tree
> VALUES (1, NULL), (2, 1), (3,1), (4,2), (5,2), (6,2), (7,3), (8,3),
> (9,4), (10,4), (11,7), (12,7), (13,7), (14, 9), (15,11), (16,11);
>
> WITH RECURSIVE t(id, path) AS (
> VALUES(1,ARRAY[NULL::integer])
> UNION ALL
> SELECT tree.id, t.path || tree.id
> FROM tree JOIN t ON (tree.parent_id = t.id)
> )
> SELECT
> t1.id, count(t2.*)
> FROM
> t t1
> JOIN
> t t2
> ON (
> t1.path[1:2] = t2.path[1:2]
> AND
> array_upper(t1.path,1) = 2
> AND
> array_upper(t2.path,1) > 2
> )
> GROUP BY t1.id;
> ERROR: unrecognized node type: 203
Thanks for the report. Here is the new patches from Yoshiyuki against
CVS HEAD. Also I have added your test case to the regression test.
> Please apply the attached patch to help out with tab
> completion in psql.
Thanks. Your patches has been included.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
Attachment | Content-Type | Size |
---|---|---|
recursive_query.patch.gz | application/octet-stream | 28.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Ryan Bradetich | 2008-07-26 03:41:57 | Re: [RFC] Unsigned integer support. |
Previous Message | Greg Sabino Mullane | 2008-07-26 02:39:34 | Re: pg_dump additional options for performance |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2008-07-26 09:05:04 | Re: pg_dump additional options for performance |
Previous Message | Greg Sabino Mullane | 2008-07-26 02:39:34 | Re: pg_dump additional options for performance |