Received-SPF: pass (loft7616.startdedicated.de: connection is authenticated)
Subject: Re: documentation for WITH RECURSIVE
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-docs@lists.postgresql.org
References: <ca53c6ce-a0c6-b14a-a8e3-162f0b2cc119@a-kretschmer.de>
 <20712.1574098328@sss.pgh.pa.us>
From: Andreas Kretschmer <andreas@a-kretschmer.de>
Message-ID: <94685a79-0b75-34ad-16bb-e1f23eb28c24@a-kretschmer.de>
Date: Mon, 18 Nov 2019 20:12:09 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <20712.1574098328@sss.pgh.pa.us>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Precedence: bulk


Am 18.11.19 um 18:32 schrieb Tom Lane:
> Andreas Kretschmer <andreas@a-kretschmer.de> writes:
>> One of our customers had problems with the syntax of WITH RECURSIVE. He
>> suggested that the documentation should be improved, maybe with this
>> sentence:
>> "If any of the CTEs is recursive, the recursive keywork must be present
>> after with", so to make sure that it does not refer to just one of the
>> named subqueries.
> Hm, was this intended for the SELECT man page (presumably in the
> "WITH Clause" section), or for section 7.8?
>
> In the SELECT page, I'd be inclined to put it after the para about
> "queries need not be ordered" and phrase it more like
>
>    If there are multiple queries in the WITH clause, RECURSIVE can
>    be written only once, immediately after WITH.  It applies to all
>    queries in the WITH clause (but has no effect on queries that do
>    not use either of these features).
>
> 			regards, tom lane

yeah, sounds good to me, thx Tom.

Regards, Andreas

-- 
2ndQuadrant - The PostgreSQL Support Company.
www.2ndQuadrant.com