Re: [RFC] What would be difficult to make data models pluggable for making PostgreSQL a multi-model database?

From: "MauMau" <maumau307(at)gmail(dot)com>
To: "Henry M" <henrymanmail(at)gmail(dot)com>, "Chris Travers" <chris(dot)travers(at)adjust(dot)com>
Cc: "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [RFC] What would be difficult to make data models pluggable for making PostgreSQL a multi-model database?
Date: 2017-09-03 20:14:53
Message-ID: 0F4F540B05294D2C82740FA2A220B28B@tunaPC
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

From: Henry M
> This may be interesting... they implement cypher (unfortunately they
had to fork in order to have cypher be a first class query language
with SQL).
>
> https://github.com/bitnine-oss/agensgraph

I'm sorry for my very late reply.

Thanks for the information. AgensGraph is certainly interesting, but
the problem is that it's a fork of PostgreSQL as you mentioned. I
wish the data models, including query languages, to be pluggable
extensions, so that various people (especially database researchers?)
can develop them flexibly. Of course, I want various data models to
be incorporated in the core as early as possible, but I'm afraid it's
not easy. If new data models can be added as extensions, they can be
developed outside the PostgreSQL community process, get popular and
mature, and then be embraced in core like GiST/SP-Gist indexes and
full text search did.

Regards
MauMau

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2017-09-03 20:47:10 Re: Optional message to user when terminating/cancelling backend
Previous Message Magnus Hagander 2017-09-03 20:03:00 Re: Function to move the position of a replication slot