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" <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-12-03 11:42:12
Message-ID: 6DBB3B4BC63F434C956D20B620CEBC06@tunaPC
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

From: Henry
Would this require a the new pluggable storage which is currently in
development or would the existing storage engine be sufficient? I am
just wondering if there are any rough design/plans for this...

I'm sorry for the long interval. The graph model can be implemented
on top of the relational storage engine, like Oracle and SQL Server
stores graph data in relational tables. But the optimal storage
engine for the graph model is required to maximize performance for
graph traversal, which introduces direct pointers between graph nodes.
So I think new level of pluggable storage is necessary.

Regards
MauMau

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-12-03 17:40:16 Re: [HACKERS] <> join selectivity estimate question
Previous Message Ashutosh Bapat 2017-12-03 11:23:36 Re: [HACKERS] advanced partition matching algorithm for partition-wise join