3 ms·

> I'm calling for an strategic discussion There is practically no information about Babelfish available to analyze. You can currently request a preview of Babe

> I'm calling for an strategic discussion There is practically no information about Babelfish available to analyze. You can currently request a preview of Babelfish if you have an AWS account, though I'm not aware of anyone having even that level of access. There is a single page placeholder on a Github.io that says "Babelfish for PostgreSQL will be available on Github in 2021". And so I genuinely don't know what a strategic discussion really means here. How much can be decided about something based on a vague press release?

_msw_ 6y ago
It is interesting to think about this in the abstract, but I think that Peter is right. The real collaboration only comes with getting the code published, design proposals on extension points in the core engine, and so on. This isn't the sort of thing that is decided with blog posts, but personally I am glad to see there is interest in this project.
ahachete 6y ago
There is information about Babelfish, including reInvent keynote, website and other sources. Here you have a 30min session about Babelfish for PostgreSQL: https://www.youtube.com/watch?v=DcGMoxPCNcQ https://www.youtube.com/watch?v=DcGMoxPCNcQ I'd also love to have more, architectural/design documents, the code itself, etc, and I'm sure they will be sooner than later released. But that doesn't prevent us, as I said, to discuss the items I suggested above. They do not depend on the source code, at all. And independently of this, there is already one thread on the -hackers mailing list that provides some information and proposes to introduce a technical improvement that not only would ease the Babelfish integration, but will also provide significant benefits for PostgreSQL itself, allowing for other protocols to come (including a potential v4 and an HTTP-based protocol): https://www.postgresql.org/message-id/CAGBW59d5SjLyJLt-jwNv%2BoP6esbD8SCB%3D%3D%3D11WVe5%3DdOHLQ5wQ%40mail.gmail.com https://www.postgresql.org/message-id/CAGBW59d5SjLyJLt-jwNv%...

_msw_ 6y ago

It is interesting to think about this in the abstract, but I think that Peter is right. The real collaboration only comes with getting the code published, design proposals on extension points in the core engine, and so on. This isn't the sort of thing that is decided with blog posts, but personally I am glad to see there is interest in this project.

ahachete 6y ago

There is information about Babelfish, including reInvent keynote, website and other sources. Here you have a 30min session about Babelfish for PostgreSQL: https://www.youtube.com/watch?v=DcGMoxPCNcQ https://www.youtube.com/watch?v=DcGMoxPCNcQ I'd also love to have more, architectural/design documents, the code itself, etc, and I'm sure they will be sooner than later released. But that doesn't prevent us, as I said, to discuss the items I suggested above. They do not depend on the source code, at all. And independently of this, there is already one thread on the -hackers mailing list that provides some information and proposes to introduce a technical improvement that not only would ease the Babelfish integration, but will also provide significant benefits for PostgreSQL itself, allowing for other protocols to come (including a potential v4 and an HTTP-based protocol): https://www.postgresql.org/message-id/CAGBW59d5SjLyJLt-jwNv%2BoP6esbD8SCB%3D%3D%3D11WVe5%3DdOHLQ5wQ%40mail.gmail.com https://www.postgresql.org/message-id/CAGBW59d5SjLyJLt-jwNv%...