x4m

7 ms·

31.
by x4m 5y ago
Currently in Odyssey password_passthrough works only for cleartext auth, PAM and LDAP. Probably, we could make this for MD5 work too. And it's the whole purpose of SCRAM to defeat this feature :) The other way to do so is auth_query -
32.
by x4m 5y ago
Hmm, yes. ParameterStatus is not sent when search_path is changed. But I think it would be trivial to patch PostgreSQL to send it. I bet one even can push such patch through commitfest.
33.
by x4m 5y ago
No. It's just about developer experience. PostgreSQL core developemnt under MacOS is just so great. You can develop PG patches completely without internet connection on a very old MacBook Air. And everything will be so blazingly fast.
34.
by x4m 5y ago
I'd certainly recommend to run pooler on the same node to avoid double encryption. Reestablishing 2x connections, dealing with 2x restarts of VM - is kind of a downside too. However it's not strictly neccesary, Odyssey can run eve
35.
by x4m 5y ago
We are also developing managed databases for US\EU market https://double.cloud/
36.
by x4m 5y ago
Sure. We use Odyssey as a component of HA cluster in Yandex.Cloud. Odyssey runs on each node of a Patroni-like system. One day we want to implement load balancing functionality in Odyssey. So that your queries go to other node if local is o
37.
by x4m 5y ago
Yes, that's a problem. We use Docker only for developement. And mostly because Odyssey is based on epoll and just will not compile on MacOS.
38.
by x4m 5y ago
Depends on how you measure performance :) pgagroal utilizes a lot of linux processes to track each connection state, we use coroutines packed into small number of processes. Actually if you have a bottleneck in multithreaded pooler - someth
39.
by x4m 5y ago
You might want to have many app backends, each with it's own Alchemy pool. This setup would create a lot of Postgres connections. When the network flaps you need to reinstall lots of TLS connections. Maybe 100ms of cpu for each handsha
40.
by x4m 5y ago
Connection pooler allows you to get more transactions per second on the same hardware. All it does - pack a lot of connections into handful of concurrently running PG backends. In theory all it does - relay bytes between sockets. But there
41.
by x4m 5y ago
This may sound naive, but implementing your own pooler is very easy e.g. in Go pgproto3 already does all packet-parsing for you. Transaction poolers are looking on ReadyForQuery packet and it's "in trnsaction" property like t
42.
by x4m 5y ago
We are going to implement config inheritance. This should bring somewhat resemblant functionality.
43.
by x4m 5y ago
There's ongoing work on making Postgres connections more scalable. I really hope that one day we will not need a pooler. https://www.citusdata.com/blog/2020/10/08/analyzing-connecti...
44.
by x4m 5y ago
FWIW I maintain Odyssey and will be happy to answer any question regarding it. Actually there was just a CVE-triggered release... I really hope to release more often with more new functionality. If you are interested in connection pooling m
45.
ClickHouse Storage for Jaeger Tracing(github.com)
31 points by x4m 5y ago|1 comments
46.
by x4m 5y ago
PostgreSQL can decode WAL to cahnged data stream on its own. Technically WAL-G can parse WAL to changes stream, but this functionality has no surface API anyhow.
47.
WAL-G 1.0 released: disaster recovery for PG, MySQL, MongoDB, MS SQL(github.com)
8 points by x4m 5y ago|0 comments
48.
Technologies That Aren’t There Yet(x4mmm.medium.com)
1 points by x4m 5y ago|0 comments
49.
by x4m 6y ago
Consider using Yandex Cloud, we offer managed Clickhouse as a service. Clickhouse is opensource DB created by Yandex.
50.
by x4m 6y ago
Thanks for the post, great read! Just one minor note s/Odessey/Odyssey/g // From Odyssey maintainer
51.
by x4m 7y ago
This year they had 3, and the year is not over yet :)
52.
by x4m 7y ago
This is cool. And we expect them to add more and more features if Odyssey will gain traction. It's about the competition. Finally, it should create enough pressure to make builtin pooler happen.
53.
by x4m 7y ago
Your claim is wrong in that "best talent" part. Though, Yandex, from time to time, loose new grads, sad but true.
54.
by x4m 7y ago
Yes, we use a cascade of PgBouncers. But it's hard to maintain, actually. Also, PgBouncer was not actively developed for years. I consider new PgBouncer features (port reuse, SCRAM-SHA-256) accomplishment of Odyssey to some (small) ext
55.
by x4m 7y ago
It's multithreaded PgBouncer.
56.
by x4m 7y ago
We were using libevent and had to remove an extra abstraction layer. Machinarium is there for two reasons: 1. Express network protocol state machine as normal control flow. Just to make code simpler. 2. Reduce contention of multithreaded op
57.
by x4m 7y ago
Pgbouncer is single-threaded. If you have 80-core box it is a huge waste to terminate your SSL in single-threaded proxy pooler.
58.
Odyssey 1.0 – scalable connection pooler for PostgreSQL(github.com)
4 points by x4m 7y ago|0 comments
59.
WAL-G v0.2 released (Postgres backup system)(postgresql.org)
4 points by x4m 7y ago|0 comments
60.
by x4m 8y ago
My name is Andrey, I'm an engineer. I'm contributing to PostgreSQL on behalf of Yandex.Cloud. Also, I'm working on WAL-G. I like jogging and quake[2,3]. Not sure what else defines me...

More ›