News for hackers. Stuff that matters.
Re:Representing Graphs in PostgreSQL by ffsm8 on Monday February 17, 2025 @11:21AM (#43080508)
What kind of data was it, of I may ask?

Graph databases have a very narrow usecase, and it's almost always in relation to people - at least ime.

Though the data type isn't really important for the performance question, the amount of data selected is. So a 6-level depth graph of connections that only connect 2-3 entities would never get into performance issues. You'd be able to go way beyond that too with such a narrow window. (3 entity Connections on 6 level join would come out to I believe ~750 rows)

If you're modeling something like movies instead, with >10 actors per production you're looking at millions of rows.

Re:Representing Graphs in PostgreSQL by derefr on Tuesday February 18, 2025 @05:42PM (#43096060)
Network analysis of financial transactions to detect "layering" (onion-routed money laundering) paths, probably.