saisrirampur

4 ms·

31.
Scaling a 1.59 quadrillion-row logging system with ClickHouse(clickhouse.com)
3 points by saisrirampur 2mo ago|0 comments
32.
PostgreSQL and the Linux OOM Killer: A Better Default(clickhouse.com)
1 points by saisrirampur 3mo ago|0 comments
33.
PostgreSQL and the Linux OOM Killer: A Better Default(clickhouse.com)
8 points by saisrirampur 3mo ago|1 comments
34.
PostgreSQL and the Linux OOM Killer: A Better Default(clickhouse.com)
3 points by saisrirampur 3mo ago|0 comments
35.
Why strict memory overcommit matters for Postgres(clickhouse.com)
2 points by saisrirampur 3mo ago|0 comments
36.
Why strict memory overcommit matters for Postgres(clickhouse.com)
2 points by saisrirampur 3mo ago|0 comments
37.
Show HN: Pg_stat_ch, a Postgres extension to export every metric to ClickHouse(github.com)
4 points by saisrirampur 3mo ago|1 comments
38.
Measuring the Impact of High Availability on Managed Postgres Performance(clickhouse.com)
2 points by saisrirampur 3mo ago|0 comments
39.
Postgres FDW: Pushdown is a negotiation(clickhouse.com)
2 points by saisrirampur 3mo ago|0 comments
40.
Huge Pages can Improve PostgreSQL Performance(clickhouse.com)
3 points by saisrirampur 3mo ago|0 comments
41.
Measuring the Performance Cost of High Availability in Postgres(clickhouse.com)
2 points by saisrirampur 3mo ago|0 comments
42.
Measuring the Performance Cost of High Availability in Postgres(clickhouse.com)
4 points by saisrirampur 3mo ago|0 comments
43.
by saisrirampur 3mo ago
Great blog! Thanks for writing this one up. Such a useful one for anyone who is build with Postgres. Succinctly reminds of all the battle scars working with many customers over the past decade. ;)
44.
Why Huge Pages Matter for Postgres?(clickhouse.com)
2 points by saisrirampur 3mo ago|0 comments
45.
Measuring the Impact of High Availability on Managed Postgres Performance(clickhouse.com)
2 points by saisrirampur 3mo ago|0 comments
46.
Why AI needs a data layer built on Postgres and ClickHouse(clickhouse.com)
1 points by saisrirampur 3mo ago|0 comments
47.
Why huge pages matter for Postgres?(clickhouse.com)
1 points by saisrirampur 3mo ago|0 comments
48.
Why Huge Pages Matter for Postgres?(clickhouse.com)
2 points by saisrirampur 3mo ago|0 comments
49.
Why Pages Matter for Postgres?(clickhouse.com)
2 points by saisrirampur 3mo ago|0 comments
50.
Pg_re2: Postgres extension for fast, RE2-powered regular expressions in Postgres(clickhouse.com)
16 points by saisrirampur 3mo ago|1 comments
51.
Why Huge Pages Matter for Postgres?(clickhouse.com)
2 points by saisrirampur 3mo ago|0 comments
52.
Two sizes fit most: Postgres and ClickHouse(clickhouse.com)
2 points by saisrirampur 3mo ago|0 comments
53.
What are Forward Deployed Engineers, and why are they so in demand? (2025)(newsletter.pragmaticengineer.com)
106 points by saisrirampur 3mo ago|98 comments
54.
Pg_re2: 9x faster regular expressions in Postgres(github.com)
2 points by saisrirampur 3mo ago|0 comments
55.
Pg_re2: 9x faster regular expressions in Postgres
1 points by saisrirampur 3mo ago|1 comments
56.
Postgres Query Observability from ClickHouse(github.com)
2 points by saisrirampur 3mo ago|0 comments
57.
by saisrirampur 3mo ago
It improved quite a lot! It scales pretty well to thousands of connections: https://techcommunity.microsoft.com/blog/adforpostgresql/imp... . However, if pooling isn’t used, there’s always an overhead (tens of mill
58.
by saisrirampur 3mo ago
Ack, we will consider offering pgdog in the future! More context on why we chose pgbouncer https://news.ycombinator.com/item?id=48873867
59.
by saisrirampur 3mo ago
We started with the most battle-tested and native option to Postgres, which is PgBouncer and tried tuning it the right way. Also now that long due kinks like support for prepared statements are solved, it’s been working really well. There a
60.
by saisrirampur 3mo ago
Ack, makes sense. I’m very curious on how this affects throughput due to a potential extra network hop from pgbouncer to Postgres. Expecting it to have a minor difference, but still curious.

More ›