levkk

7 ms·

31.
by levkk 3mo ago
I cancelled Claude. The harness is kinda broken, GPT 5.5 is good, and GLM 5.2/Deepseek is good too (with pi, especially). Just not worth the trouble. And I'm not going to pay two subscriptions.
32.
by levkk 3mo ago
CRUD apps don't usually delete in bulk. It's also hard to structure partitions in a way that doesn't wipe out months of important business data -- this is why teams often ETL their DB into Snowflake/ClickHouse and only t
33.
by levkk 3mo ago
You can have multiple. All sharding is config-based, so no real-time synchronization is required.
34.
by levkk 3mo ago
This just checks if the package is installed, not if the installed version is infected. Presumably, if you (me...) haven't run `yay -Syu` in a while (months), we're fine, right? ...Right? Goddamit, don't make me reinstall Arc
35.
by levkk 3mo ago
I didn't realize there are _any_ managed providers of PgDog out there...do tell!
36.
by levkk 3mo ago
Awesome, glad it worked!
37.
by levkk 3mo ago
We also do that! But it's not well documented at the moment.
38.
by levkk 3mo ago
Thanks! Glad we made it relatively easy to migrate!
39.
by levkk 3mo ago
For sure. They should be used for "metadata"-style tables only. High throuput writes should be direct-to-shard.
40.
by levkk 3mo ago
Yeah good callout. We'll add rendezvous soon enough. Until then, being compatible with Postgres partitions has been advantageous -- while we build everything out, people were able to migrate to PgDog for the query routing layer while d
41.
by levkk 3mo ago
Not yet, but actively working on this as we speak.
42.
by levkk 3mo ago
fwiw, we support cross-shard transactions. They are not magic though, just good old 2pc and a bit of coordination.
43.
by levkk 3mo ago
Thanks!
44.
by levkk 3mo ago
This reminds me of college. We had to cite our own papers from prior semesters or risk getting kicked out for plagiarism. I don't miss those days :)
45.
by levkk 3mo ago
Thanks! Yup...to be expected. If you know, you know, and have the scars to prove it :)
46.
by levkk 3mo ago
Yup!
47.
by levkk 3mo ago
Two big ones: 1. Control plane to manage multi-node deployments; "works out of the box" experience to make PgDog easy to deploy and use 2. QoS (quality of service): automatically block bad queries from taking down the database Las
48.
by levkk 3mo ago
Good thing we support HA as well: https://docs.pgdog.dev/features/load-balancer/ Load balancer with health checks and failover, works out of the box. :) Battle-tested at this point too, so could be worth a look.
49.
by levkk 3mo ago
I see you met Sage, our newest founding engineer :) If you're not having fun at your job... In all seriousness, we review every single line of code that goes in and only people who work for PgDog Inc are allowed to merge.
50.
by levkk 3mo ago
Yup. We support schema-based sharding: https://docs.pgdog.dev/configuration/pgdog.toml/sharded_sche...
51.
by levkk 3mo ago
Not the place and not the time, but we are building an enterprise edition that "just works" out of the box. Not saying that the open source experience cannot be better - it always can and we'll keep improving. What you'v
52.
by levkk 3mo ago
Always is. Marketing is not our strong suit (only engineers here). We'll get better at it.
53.
by levkk 3mo ago
> 8 smaller boxes handling ~500GB each and then one medium box for the proxy? That's exactly right. Get in touch (lev@pgdog.dev), happy to help or at the very least tell you what current works (or doesn't) so you know what your
54.
by levkk 3mo ago
This is not an extension, it's a proxy! Very different. You can deploy it anywhere already without having to wait for upstreaming or your cloud provider adding support for it. It's one of the two reasons why we built it this way,
55.
by levkk 3mo ago
Yes, except it doesn't have any cross-dependencies on the same volume, so the uptime here should be higher.
56.
by levkk 3mo ago
OLAP means different things to different people. For us, it's just making sure your admin dashboard keeps working basically: SELECT tenant_id, COUNT(clicks) FROM users GROUP BY tenant_id ORDER BY 2 DESC LIMIT 25; Perform
57.
by levkk 3mo 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.
58.
by levkk 3mo 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.
59.
by levkk 3mo 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
60.
by levkk 3mo 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

More ›