From: | "Deep-Impact" <sakasaumau2009(at)clear(dot)ocn(dot)ne(dot)jp> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "MauMau" <maumau307(at)gmail(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 22:35:55 |
Message-ID: | B26BD590D3814583B665927CCDBF3577@tunaPC |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
From: Tom Lane
It sounds like what you want is to replace all of Postgres except
the name. I'm not clear on the point.
The point is to make PostgreSQL a versatile database suitable even for
niche use cases. I want more people to love and rely on PostgreSQL.
Ideally, I want to see various data models incorporated in core from
the beginning, but it would be difficult. So, this pluggable data
model is necessary to foster data model development both inside and
outside the PostgreSQL community. With that said, I hope PostgreSQL
will someday absorb those data models, just like PL/pgSQL is now in
core.
But for now, I think the relational data model will continue to play a
central role. I don't think it's worth making the current relational
data model implementation a plugged module. It will depend on the
software design and source code cleanness whether to do that.
I don't understand yet how painful it would be to support other data
models as first-class citizens, and I may be a reckless man who
doesn't know fear. So I wish you could help and pave this difficult
way together.
Regards
MauMau
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2017-12-03 22:48:29 | Re: pg_dumpall -r -c try to drop user postgres |
Previous Message | Vitaliy Garnashevich | 2017-12-03 22:11:47 | Re: Bitmap scan is undercosted? |