Re: [RFC] What would be difficult to make data models pluggable for making PostgreSQL a multi-model database?
От | Deep-Impact |
---|---|
Тема | Re: [RFC] What would be difficult to make data models pluggable for making PostgreSQL a multi-model database? |
Дата | |
Msg-id | B26BD590D3814583B665927CCDBF3577@tunaPC обсуждение исходный текст |
Ответ на | Re: [HACKERS] [RFC] What would be difficult to make data models pluggable for making PostgreSQL a multi-model database? (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [RFC] What would be difficult to make data models pluggable formaking PostgreSQL a multi-model database?
|
Список | 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
В списке pgsql-hackers по дате отправления: