tee-es-gee

8 ms·

1.
Show HN: Pg_deltax, Apache-licensed alternative to TimescaleDB(github.com)
39 points by tee-es-gee 4mo ago|1 comments
2.
Postgres minor releases closing 11 CVEs(postgresql.org)
26 points by tee-es-gee 4mo ago|0 comments
3.
by tee-es-gee 5mo ago
It looks like pgBackRest will likely continue, multiple companies are stepping up with sponsorships. Mentioning this just in case anyone is making plans to move away, it's probably worth waiting a bit for things to settle.
4.
Xatastor: ZFS and NVMe-Of for Postgres Databases(xata.io)
6 points by tee-es-gee 5mo ago|0 comments
5.
by tee-es-gee 5mo ago
I do think that as service providers we now have a new "attack vector" to be worried about. Up to now, having an API that deletes the whole volume, including backups, might have been acceptable, because generally users won't
6.
by tee-es-gee 5mo ago
I agree and hope this is the case for anything serious enough. I also don't see this changing any time soon. There are ways to give safe access to the data, at least read-only, that don't involve production risk and don't sac
7.
by tee-es-gee 5mo ago
Looks interesting! Do you have ClickBench results or similar? > Everything in core, no extensions. HTTP(S), S3 (anonymous public reads), Avro, Excel, Arrow, and SQLite read through the same core binary - no separate install/load ste
8.
Code review advice for vibe coders(xata.io)
3 points by tee-es-gee 5mo ago|0 comments
9.
Xata – open-source, cloud native, Postgres platform(github.com)
3 points by tee-es-gee 5mo ago|0 comments
10.
by tee-es-gee 5mo ago
I will follow this one for sure. There are a few more companies with the extremely ambitious goal of "a better AWS", and I am interested in the various strategies they take to approach that goal incrementally. A service offering V
11.
by tee-es-gee 5mo ago
Nice article! From what I understand, you computed the bloom values in the application layer, right? Would https://www.postgresql.org/docs/current/bloom.html have worked as well?
12.
Open source Postgres platform with branching(xata.io)
2 points by tee-es-gee 5mo ago|0 comments
13.
by tee-es-gee 5mo ago
Got it, yes, I've seen in the other comment that you're referring to the new Postgres 18 feature. If that works for you in local dev, so much the better :)
14.
by tee-es-gee 5mo ago
Yes, for sure, and stuff like this is really useful when rebalancing storage nodes, for example. My point is that for the use case of offering a Postgres service with CoW branching as a key feature, you can't really escape some form of
15.
by tee-es-gee 5mo ago
We have an overview on how it works here: https://xata.io/blog/open-source-postgres-branching-copy-on-...
16.
by tee-es-gee 5mo ago
> You don’t need anything but vanilla pg and a supported file system to do it anymore; just clone the database using a template and a newish version of Postgres. Are you referring to `file_copy_method = clone` from Postgres 18? For examp
17.
by tee-es-gee 5mo ago
Xata is open source btw (open core): https://github.com/xataio/xata
18.
by tee-es-gee 5mo ago
For context for the others, I think you are referring to this blog post: https://xata.io/blog/open-source-postgres-branching-copy-on-... (in particular the "The key is in the storage system" section) right? W
19.
Postgres copy-on-write branching explained(xata.io)
1 points by tee-es-gee 5mo ago|0 comments
20.
What if database branching was easy?(xata.io)
70 points by tee-es-gee 5mo ago|57 comments
21.
What if database branching was easy?(xata.io)
2 points by tee-es-gee 5mo ago|0 comments
22.
Show HN: Xata, open-source Postgres platform with copy-on-write branches(github.com)
4 points by tee-es-gee 5mo ago|0 comments