I'd love to! But MySQL is developed inside Oracle, and OCA somewhat scares me. Perhaps, I'll give a try to MariaDB or other forks.

And there's also https://postgrespro.com/docs/enterprise/current/multimaster With a history behind it.

Right, I'm not so familiar with it but from that page:

> The replication mechanism is based on logical decoding and an earlier version of the pglogical extension provided for community by the 2ndQuadrant team.

I think this should run just fine, why not? As long as you have proper Postgres operator, such proxy will run normally on top of that.

Interested in contributing/co-writing such a runbook for StackGres? [1]

[1]: https://stackgres.io/doc/latest/runbooks/

+1

there's already well maintained extension https://github.com/fboulnois/pg_uuidv7

It's slightly different from recommendations by draft RFC version (there's no counter), but fully within spec requirements. From practical point there's no difference at all.

FWIW Steam Deck runs 8k transactions per second if you build Postgres there. A nice place to work on open source development, actually. https://twitter.com/x4mmmmmm/status/1620984546216017921

Nice, now I can write off a Steam Deck as a business expense!

> Reduce the memory usage of prepared queries

FWIW Odyssey supports prepared statements in transaction pooling.

I concur that Odyssey docs are insufficient to build a big picture. But I'm trying to answer every question in the Internets about Odyssey :) Documenting is hard - everything seems obvious to me, but understand that may things are not that obvious. // Odyssey maintainer

I think the book is free because Egor and PostgresPro want to develop the community. If you want to pay back - you can just start contributing to Postgres. No need to wait :)

You are running on up to date version which seems to have no known critical bugs.

Just revert d9d0762 or use actual REL_14_STABLE.