levkk

6 ms·

61.
by levkk 4mo ago
Two schools of thought: 1. Let it crash. Increase the RAM, try again. 2. Page to disk (swap), make it slow but ultimately work. Both have their trade-offs. There is no free lunch here.
62.
by levkk 4mo ago
The docker compose example is just a demo. I don't know anyone who runs Postgres with docker compose / swarm in prod :) But yes, happy to add volumes so it seems more real.
63.
by levkk 4mo ago
We do, just buried deep in our blog: https://pgdog.dev/blog/pgdog-vs-citus The same old processes vs. threads debate, plus having the ability to scale the coordinator past a single machine. So, if you're OLTP, def
64.
by levkk 4mo ago
Depends. Only pooling, very little. Load balancing/sharding needs to parse queries, so a bit more. Could go up to a GB per pod, sometimes more if you have a lot of unique SQL queries (unique by text, not by parameters). We cache query
65.
by levkk 4mo ago
Old benchmark, but still good: https://pgdog.dev/blog/pgbouncer-vs-pgdog
66.
by levkk 4mo ago
We should add it to brew/apt/etc for sure. Also, we could add it to crates.io so you could do something like `cargo install pgdog`. Distribution, distribution, distribution.
67.
by levkk 4mo ago
Sorry, out walking the dog (not a pun). I'll post more details in a few.
68.
by levkk 4mo ago
Getting there! Cross-shard writes do because of 2pc. Reads are eventually consistent.
69.
by levkk 4mo ago
Crap! Missed opportunity.
70.
by levkk 4mo ago
Not quite. The performance gain is to bring those features to Postgres! Edit: Performance gains are from having the ability to load balance reads (horizontal scaling for read queries) and scale out writes (with sharding). Once instance bott
71.
PgDog is funded and coming to a database near you(pgdog.dev)
548 points by levkk 4mo ago|261 comments
72.
by levkk 4mo ago
2026 is the year of the Postgres queue! (DBOS[0], pgQue[1]) It's awesome that the community is contributing this and giving us the option to use it. As an ex-app engineer though, I kind of prefer my queue logic to be in code, in Git, b
73.
PostgreSQL and the OOM Killer: Why We Use Strict Memory Overcommit(ubicloud.com)
5 points by levkk 4mo ago|3 comments
74.
by levkk 4mo ago
I don't understand this obsession with SQLite for real, production apps. SQLite is an embedded database, completely unsuitable for managing concurrency. This is what database _servers_ are for, e.g., Postgres, MySQL, etc. Their entire
75.
by levkk 4mo ago
It wouldn't, at least not directly. That's why it wasn't done pre-AI.
76.
by levkk 4mo ago
I'm getting to a point in my life (age) where I want to put my money into things I care about. Netflix? 25$/mo, 3 hours a day. Search 10$/mo? 8 hours a day. Easy.
77.
by levkk 4mo ago
DigitalOcean. Seriously. They have been around a long long time and built a lot of the core infrastructure you rely on every day (e.g. Ceph).
78.
by levkk 5mo ago
I'm using GitHub for my business and so do millions more. Might be time to prioritize paying customers, historically popular open source repos and PRs created by known human actors. Agents can wait, humans have much less patience.
79.
by levkk 5mo ago
Last time I checked, Barman didn't support backups to S3. That's why (for us) pgBackRest was such a big deal: it could offload full and incremental backups to a basically limitless and reliable medium. I think (and I'm probab
80.
by levkk 5mo ago
Shameless plug[0]. [0] https://pgdog.dev
81.
by levkk 5mo ago
This is just a language server problem. I'm sure you can configure whatever language server PHP is using to disable specific warnings, etc.
82.
by levkk 5mo ago
Amazing project that spawned entire companies. We used it to build postgresml[0] and most Postgres extensions are built on top of it these days. [0] https://github.com/postgresml/postgresml
83.
by levkk 5mo ago
On top of it, intel chips are not competitive with apple silicon. Why buy a laptop that's 30% slower and uses more energy for the same price?
84.
Shard Postgres with One Command(pgdog.dev)
1 points by levkk 5mo ago|0 comments
85.
Reshard Button(pgdog.dev)
2 points by levkk 6mo ago|0 comments
86.
by levkk 6mo ago
I'm paying for Netflix to do that as a feature. Instagram uses that to drive engagement to sell ads. Disabling personalized content on Netflix is a revenue-neutral choice. On Instagram, that would mean their ad revenue takes a huge div
87.
by levkk 7mo ago
Lobsters is like that, basically a ghost town compared to Reddit. If you block engagement, you will succeed.
88.
by levkk 7mo ago
It's not clear to me how this is verifiable without constant hardware supervision. Even that'll get cracked, just like DVD encryption back in the day. You almost need dedicated hardware that can't run any other software excep
89.
We fixed Postgres connection pooling on serverless with PgDog(circleback.ai)
3 points by levkk 7mo ago|0 comments
90.
by levkk 7mo ago
As the tool gets better, people trust it more. It's like Tesla's self-driving: "almost" works, and that's good enough for people to take their hands off the wheel, for better or for worse. The "almost" par

More ›