Postgres as a Graph Database: (Ab)Using PgRouting

Re:Postgres as a Graph Database: (Ab)Using PgRouting by henryfjordan on Thursday February 27, 2025 @07:59PM (#43200431)

We basically had a single table that we wanted to be able to nest on itself arbitrarily. Think categories and subcategories, maybe 100k nodes/rows

Postgres worked fine but cypher is so much more expressive and handles stuff like loop detection for you, neo4j was much easier to work with. Performance wasn't ever really an issue with either.

[ Parent | on HN ]

Re:Postgres as a Graph Database: (Ab)Using PgRouting by AlphaSite on Thursday February 27, 2025 @10:28PM (#43201378)

We have something similar in Postgres but IMO disconnectedness also plays a really big part in this whole calculation. We actually ended up just changing the transitive closure for fast operations (and simpler code).

[ Parent | on HN ]

Re:Postgres as a Graph Database: (Ab)Using PgRouting by zozbot234 on Friday February 28, 2025 @05:24AM (#43203992)

Note that more recent versions of Postgres have added support for the CYCLE keyword, for easier loop detection.

[ Parent | on HN ]