11–20 of 32 posts
This is awesome. We were just looking at throwing up PgBouncer in front of RDS in the coming year. Looking forward to PostgreSQL support!
TL;DR: AWS now has a managed connection pooling service for MySQL on RDS only (public preview right now). The article talks about using it in conjunction with Lambda.
This is awesome. We were just looking at throwing up PgBouncer in front of RDS in the coming year. Looking forward to PostgreSQL support!
As an aside, why isn't pgbouncer basically built into Postgres, at least as an option? I'm sure there's a good reason, but as a lay-user, pgbouncer seems to just do connections better than Postgres. It's just a pain to both with it when cloud databases are so easy to launch in comparison.
Earlier quoted context omitted.
As an aside, why isn't pgbouncer basically built into Postgres, at least as an option? I'm sure there's a good reason, but as a lay-user, pgbouncer seems to just do connections better than Postgres. It's just a pain to both with it when cloud databases are so easy to launch in comparison.
Culture in Pg community once favored separate, single purpose solutions. This was the replication story for a long time. So here's hoping they'll build-in something to help with the high costs of individual connections.
This is awesome. We were just looking at throwing up PgBouncer in front of RDS in the coming year. Looking forward to PostgreSQL support!
I really hope it can replace PgBouncer. We've spent way too much time getting it running in ECS, mostly due to us needing a separate PgBouncer service for the primary and replica RDS instances. And then a third ECS service running HAProxy in TCP mode to load balance between the PgBouncer services, to provide a read-only endpoint that balances between the primary and replica. Add issues like: having to patch in HAProx…
Does anyone know why RDS Postgres always seems to lag behind their MySQL offering? I can imagine Postgres is that much more difficult to develop a connection pooling service for, especially since PGBouncer and PGPool-II both already exist and are widely used.
This is awesome. We were just looking at throwing up PgBouncer in front of RDS in the coming year. Looking forward to PostgreSQL support!
I really hope it can replace PgBouncer. We've spent way too much time getting it running in ECS, mostly due to us needing a separate PgBouncer service for the primary and replica RDS instances. And then a third ECS service running HAProxy in TCP mode to load balance between the PgBouncer services, to provide a read-only endpoint that balances between the primary and replica. Add issues like: having to patch in HAProx…
The result format is a bit clunky but there's all the column information you'd expect.
I found this golang database interface which ended up dropping in as expected with a few tweaks.
https://github.com/Clever/rds/tree/birthday
My bill for Aurora Serverless Postgres last month was less than a dollar.