Have it as a part of Postgres core distribution?

[NikolayS]

Hi,
what is the current status of this project and how soon it might be included in the Postgres core?

I've just had a chat with Amazon RDS support, and while they have a pretty long list of already supported Postgres extensions, they say that it's pretty hard for them to include contribs written in C (hehe), so for large number of Postgres users living in clouds (RDS, Heroku and now GCP) the only way to use RUM is to have it as a part of Postgres.

[za-arthur]

Hello,
RUM is in development state now. I don't believe that it could be included in the PostgreSQL core in the near future.
RUM was started as a patch for GIN several years ago actually. But PostgreSQL's hackers didn't reach agreement about architecture of new changes. And so RUM is an extension now.

[NikolayS]

Ok but what if it will be an extension distributed with -contribs standard package? It's a pity that you guys currently don't have plans to attack -hackers with new proposal. As I've said, a lot of users cannot compare le C extensions, they need packaging (and ideally, postgres-contribs, not a separate package).

…

On Wednesday, April 19, 2017, Arthur ***@***.***> wrote: Closed #14 <#14>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#14 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABSHem2bkFbAQjWAfhHyGXAHLretN_CEks5rxh2pgaJpZM4MxyV7> .

[NikolayS]

*compile a C extension On Wednesday, April 19, 2017, Nikolay Samokhvalov <samokhvalov@gmail.com> wrote:

…

Ok but what if it will be an extension distributed with -contribs standard package? It's a pity that you guys currently don't have plans to attack -hackers with new proposal. As I've said, a lot of users cannot compare le C extensions, they need packaging (and ideally, postgres-contribs, not a separate package). On Wednesday, April 19, 2017, Arthur ***@***.*** ***@***.***');>> wrote: > Closed #14 <#14>. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#14 (comment)>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/ABSHem2bkFbAQjWAfhHyGXAHLretN_CEks5rxh2pgaJpZM4MxyV7> > . >

[obartunov]

On Wed, Apr 19, 2017 at 6:47 PM, Nikolay ***@***.***> wrote: Ok but what if it will be an extension distributed with -contribs standard package? It's a pity that you guys currently don't have plans to attack -hackers with new proposal. As I've said, a lot of users cannot compare le C extensions, they need packaging (and ideally, postgres-contribs, not a separate package).

We don't have enough resources to convince hackers right now. Also, we are waiting for the two new big features - better custom WAL format and supports of arrays, hopefully in a couple of weeks. Notice, today we released supports of many built-in data types. After that we'll need somebody's help to write docs and only then we could start discussion in -hackers.

…

On Wednesday, April 19, 2017, Arthur ***@***.***> wrote: > Closed #14 <#14>. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#14 (comment)>, or mute > the thread > > <https://github.com/notifications/unsubscribe-auth/ABSHem2bkFbAQjWAfhHyGXAHLretN_CEks5rxh2pgaJpZM4MxyV7> > . > — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.