Gunther Schadow writes:
> Also, why even use the RECURSIVE keyword, DB2 didn't need it, and the
> query analyzer should immediately see the recursion, so no need to have
> that keyword.
Our reading of the SQL spec is that it's required. The scope of
visibility of CTE names is different dependi
On 12/28/2022 10:48 AM, Justin Pryzby wrote:
Maybe the new parameter in v15 would help.
https://www.postgresql.org/docs/15/runtime-config-query.html#GUC-RECURSIVE-WORKTABLE-FACTOR
recursive_worktable_factor (floating point)
Sets the planner's estimate of the average size of the working tab
On Wed, Dec 28, 2022 at 10:39:14AM -0500, Gunther Schadow wrote:
> I have a complex query which essentially runs a finite state automaton
> through a with recursive union, adding the next state based on the
> previous. This is run at 100,000 or a million start states at the same
> time, picking a
I have a complex query which essentially runs a finite state automaton
through a with recursive union, adding the next state based on the
previous. This is run at 100,000 or a million start states at the same
time, picking a new record (token), matching it to the FSA (a three-way
join:
to
