Re: [PATCHES] WITH RECUSIVE patches 0717

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: ishii(at)postgresql(dot)org, er(at)xs4all(dot)nl, 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 0717
Date: 2008-07-20 23:19:35
Message-ID: 20080721.081935.116359430.t-ishii@sraoss.co.jp
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

> > Thus I think we should avoid this kind of ORDER BY. Probably we should
> > avoid LIMIT/OFFSET and FOR UPDATE as well.
>
> What of index-optimized SELECT max(...) ?

Aggregate functions in a recursive term is prohibited by the
standard. For example,

WITH RECURSIVE x(n) AS (SELECT 1 UNION ALL SELECT max(n) FROM x)
SELECT * FROM x;

produces an error.
--
Tatsuo Ishii
SRA OSS, Inc. Japan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2008-07-21 00:00:05 Re: [PATCHES] WITH RECUSIVE patches 0717
Previous Message Josh Berkus 2008-07-20 22:38:00 Re: CommitFest dragging?

Browse pgsql-patches by date

  From Date Subject
Next Message David Fetter 2008-07-21 00:00:05 Re: [PATCHES] WITH RECUSIVE patches 0717
Previous Message Simon Riggs 2008-07-20 21:59:40 Re: pg_dump additional options for performance