Re: wCTE behaviour - Mailing list pgsql-hackers

From Greg Smith
Subject Re: wCTE behaviour
Date
Msg-id 4CFBDB03.3000902@2ndquadrant.com
Whole thread Raw
In response to Re: wCTE behaviour  (Marko Tiikkaja <marko.tiikkaja@cs.helsinki.fi>)
Responses Re: wCTE behaviour  (David Fetter <david@fetter.org>)
List pgsql-hackers
Marko Tiikkaja wrote:
> This is almost exactly the patch from 2010-02 without 
> CommandCounterIncrement()s.  It's still a bit rough around the edges 
> and needs some more comments, but I'm posting it here anyway.
>
> This patch passes all regression tests, but feel free to try to break 
> it, there are probably ways to do that.  This one also has the "always 
> run DMLs to completion, and exactly once" behaviour.

So this patch was marked "Ready for Committer", but a) no committer has 
picked it up yet and b) Marko has made changes here that nobody else has 
tested out yet that I've seen on the last.  Accordingly, that 
classification may have been optimistic.  It seems to me that another 
testing run-through from someone like David might be appropriate to 
build some confidence this latest patch should be a commit candidate.  
If there is a committer intending to work on this as-is, they haven't 
identified themselves.

-- 
Greg Smith   2ndQuadrant US    greg@2ndQuadrant.com   Baltimore, MD
PostgreSQL Training, Services and Support        www.2ndQuadrant.us




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: WIP patch for parallel pg_dump
Next
From: Josh Berkus
Date:
Subject: Re: profiling connection overhead