Re: Bug: Missing check_stack_depth() in GRAPH_TABLE rewriter
Peter Eisentraut <peter@eisentraut.org>
From: Peter Eisentraut <peter@eisentraut.org>
To: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>,
SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-04-24T06:24:13Z
Lists: pgsql-hackers
On 15.04.26 17:07, Ashutosh Bapat wrote: > Thanks for the report. I could reproduce the segfault on my laptop. > The attached patch fixes it and gives ERROR: stack depth limit > exceeded. > > generate_queries_for_path_pattern_recurse() - has to work in a linear > fashion since the elements need to be processed in an order. Each > permutation of elements produces one query. These queries can be > arranged in a balanced tree as you suggest OR when constructing the > setop tree we could generate it in divide-and-conquer manner. However, > the tree will be flattened in the planner anyway (See > flatten_simple_union_all() and pull_up_simple_union_all()). Thus the > final planning will require a deeper stack anyway. The code complexity > doesn't seem to be worth it. > > I also looked at a few commits that add check_stack_depth() to see if > we add tests for these scenarios. But I didn't find any. So no tests > added with this commit. committed (I moved the #include "miscadmin.h" to a more alphabetical position.)
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Check for stack overflow when rewriting graph queries
- 2ff289d03939 19 (unreleased) landed