ahachete

6 ms·

1.
by ahachete 5d ago
> schema changes locking Schema changes need locking... everywhere. Citus is no different. And they need proper design everywhere. If you mean that it requires distributed transactions, well, yes, again: expected and solved . Not even a
2.
by ahachete 5d ago
If you want an OSS sharded Postgres, just use Citus. Feature-full, proven, mature, boring.
3.
by ahachete 6d ago
But it's not really accurate: > This adds some undesirable side effects, however. First, the coordinator becomes the bottleneck. Apart from being able to use any node as a coordinator (and you can load balance them to avoid having &
4.
by ahachete 12d ago
Yeah, and I don't see how that changes my question, which still holds: did you try to fix the first project, and report the issues, before doing a full rewrite?
5.
by ahachete 14d ago
I assume you have reported the issues / crashes to pgcopydb. Wasn't it easier to fix them rather than rewriting from scratch? I assume rewrite was heavily AI driven, and if so, probably AI could have fixed pgcopydb rather than rew
6.
by ahachete 20d ago
Good job, Colin. I see you are following the Dyna53 [1] steps ;) What a school of thought you have sparked, Corey! [1]: https://dyna53.io/
7.
by ahachete 2mo ago
Same here. Stopped reading.
8.
by ahachete 2mo ago
I feel ya. I'm always middle clicking twice, story and comments. This shouldn't be a script (no offense, great job!). It should be built into the browsers!
9.
by ahachete 2mo ago
AGPL and copyleft licenses are not restrictive , they provide forward (open source) guarantees . The only thing they "restrict" is the ability to remove freedoms. Therefore is not a restriction, is a guarantee. A guarantee that
10.
by ahachete 3mo ago
> note that the local NVMe setup does have backups and WAL-archival to S3, which provides data-durability with RPO of 10s of seconds. That's good, it provides a reasonable level of RPO, although I prefer just 0. But with this the RT
11.
by ahachete 3mo ago
My 2 cents: > Each run lasts 10 minutes, long enough to move past warmup and capture stable throughput But short enough not to show the effect of checkpoints (which is quite noticeable). It's not representing a realistic workload. I
12.
by ahachete 3mo ago
At StackGres [1] we find Timescale to be one of the most used extensions. Timescale is quite a successful project! StackGres is actually the first solution recommended by Timescale for self-hosting with Kubernetes operators [2]. So if you a
13.
by ahachete 3mo ago
TBH I don't think it's that straightforward, I see it more of a notable architectural change. At a very high level, this means: * Adding a sharding function, as you say. * Developing an external service for metadata (shard placeme
14.
by ahachete 3mo ago
I have mentioned this before, but here it goes again: I'm really happy that there's more options for Postgres sharding and I applaud Pgdog and the team's efforts and energy. Having said that, this makes it a no-go for me: &gt
15.
by ahachete 3mo ago
> having the ability to scale the coordinator past a single machine Since Citus v11 (released 4 years ago), any worker node can also work as a "query router" (a node that you can query against [1], and works from this perspecti
16.
by ahachete 5mo ago
> You definitely don't want to run a production system at saturation! But it's worthwhile to measure a complex system like Postgres at saturation, see when it gets there and how it behaves there, and then run at a slightly lowe
17.
by ahachete 5mo ago
> we find a Postgres server can handle up to 144K of these writes per second. That’s a lot, equivalent to 12 billion writes per day. Based on the shown graph, this is misleading at best, essentially false. After 120K writes/s p50 sp
18.
by ahachete 5mo ago
Yeah, I know. Welcome to the club :( https://x.com/ahachete/status/2035783292549755228
19.
Dockerhub was blocked yesterday in Spain because of football games(twitter.com)
2 points by ahachete 6mo ago|0 comments
20.
by ahachete 7mo ago
> The extension model is great, but it doesn't work with existing postgres providers (RDS, Aurora, etc.). Unless one such extension becomes standard enough that all providers will support it. That would be ideal, IMO. That's tr
21.
by ahachete 7mo ago
IMO transparent proxies for observability are not the best pattern. And I speak from experience, we developed the Postgres plugin for Envoy [1], [2] and we use it in StackGres [3], among others, for this very same reason, observability. The
22.
Apache Doris Up to 40x Faster Than ClickHouse(velodb.io)
1 points by ahachete 8mo ago|0 comments
23.
by ahachete 8mo ago
Postgres can really scale well vertically (and horizontally for read-only workloads) as the post shows. However, I'm still surprised about the reasons for not sharding. They have been mentioned before, but I haven't seen a substan
24.
by ahachete 8mo ago
Java (modern Java) would be awesome!
25.
by ahachete 8mo ago
I'd also try it, but I'm Linux only ^_^
26.
by ahachete 8mo ago
Not my experience. It's junior level coding and maybe senior level advising, but even then only when clearly directed with the right questions and guardrails. As an autonomous thing? Junior at best. That's why I think it's ex
27.
by ahachete 8mo ago
There's a fundamental disconnect: OP refers to senior engineers being replaced with AI, whereas the evidence and logical reasoning points much more to junior engineers being replaced by AI. And that premise seems like a quite plausible
28.
by ahachete 9mo ago
Thank you for acknowledging this and updating the blog post correspondingly. I'd love to test and compare PeerDB with Debezium (Embedded), and even SynchDB. But as said, the licensing is a blocker for us. And given the focus and bandwi
29.
by ahachete 9mo ago
> "As part of the acquisition, we made an important decision: not only to keep PeerDB open source" > "Here goes the Open Source reference to our validation logic." > "PeerDB Open Source Repository" I h
30.
by ahachete 9mo ago
"Most components" seems a bit of an understatement when compared with the Framework. Sure, some components can be replaced. And not at the same cost (opening and manipulating the Framework vs the ThinkPad). But not all, like the m

More ›