Re: SEARCH and CYCLE clauses

Vik Fearing <vik@postgresfriends.org>

From: Vik Fearing <vik@postgresfriends.org>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2021-02-22T10:05:09Z
Lists: pgsql-hackers

Attachments

On 2/22/21 9:44 AM, Peter Eisentraut wrote:
> On 22.05.20 14:32, Peter Eisentraut wrote:
>>> As an improvement over the spec, I think the vast majority of people
>>> will be using simple true/false values.  Can we make that optional?
>>>
>>>      CYCLE f, t SET is_cycle USING path
>>>
>>> would be the same as
>>>
>>>      CYCLE f, t SET is_cycle TO true DEFAULT false USING path
>>
>> I was also considering that.  It would be an easy change to make.
> 
> This change has been accepted into the SQL:202x draft.

Yay!

> Here is a patch for it.

This looks good to me, except that you forgot to add the feature stamp.
 Attached is a small diff to apply on top of your patch to fix that.
-- 
Vik Fearing

Commits

  1. Enhanced cycle mark values

  2. SEARCH and CYCLE clauses

  3. doc: Expand recursive query documentation

  4. Adjust cycle detection examples and tests