Heh Heh Heh

Back in the early days PostgreSQL was a NoSQL database called Postgres, using a query language called POSTQUEL.

Then SQL was added, becoming PostgreSQL.

With Agens Graph adding an optional non-SQL query language back to it, it seems like it's gone a full circle. Hopefully on an upward slope though. :)

If anyone's interested in the pre-SQL Postgres, there's some info here: https://www.postgresql.org/about/history/

Can someone speak to how Agens compares to Neo4j? Since from a quick glance they seem to be using some of Neo's features.

I'd be interested in seeing performance comparisons as it seems Agens is implemented in C.

Here's slides from a recent talk on it: https://www.percona.com/live/17/sites/default/files/slides/A...

I've been following this for a few months.

It looks neat but too new to entrust to any major project in my opinion. Also seems too new to put together and meaningful performance comparison since it still seems they're finding frequent improvements.

I really wished this could have been distributed as an extension rather than a totally separate Postgres package. It is much easier to play with extensions... I read somewhere they can't do it since they have to modify non-extensible bits of code:(

This is awesome. So many of the problems in legacy projects that I've had to deal with have been from trying to shoehorn a graph business process into a tree database.

Wondering if anyone has experience with it... there's a lot of competition in graph database market, curious to see if this is worth investing time in.

Postgres having recursive CTE's made graph querying with SQL actually pretty tenable. I designed a graph like schema for a company I worked at awhile ago now with postgres and recursive CTE's in mind. Worked relatively well though some queries were quite large.

Interesting .. is the team considering Gremlin support as well .. It is sort Of a standard with Graph DBs