Postgres: The Graph Database You Didn't Know You Had

Re:Postgres: The Graph Database You Didn't Know You Had by jeremyjh on Friday March 31, 2023 @01:36PM (#35390360)

I think GP means that it has to completely expand the recursive part for every branch before any where condition on the edge nodes can be applied. Graph databases presumably can optimize this.

I've found recursive queries to be difficult to scale in real-world queries past a few million edge nodes. We've denormalized several tree relationships so that the edge is connected both to its parent and to the root of its tree in several cases.

[ Parent | on HN ]

Re:Postgres: The Graph Database You Didn't Know You Had by afandian on Friday March 31, 2023 @06:49PM (#35394813)

Thanks! Sounds like you're saying that brute-force recursive algorithms without backtracking or early termination aren't a good match for path finding. That's not a surprise.

I'm using recursive algorithm on Postgres to find trees in a graph, but only where I'm specificaly interested in all of the nodes.

[ Parent | on HN ]