73 points by craigkerstiens about 6 hours ago | 8 comments | View on ycombinator
jzelinskie about 3 hours ago |
aurareturn about 3 hours ago |
I thought it would be a simple process but it ended up taking many hours and a few retries. Holy hell it was a miserable experience and it ruined my New Years Eve.
I’m so happy this is now built in.
inkysigma about 2 hours ago |
dap about 2 hours ago |
QuentinM about 2 hours ago |
Sadly it doesn’t support partitions yet, which is typical when reaching sufficient scale that bloat management really matters. People often mention disk space when talking about dead tuples, but the real killer is what’s hidden under - bloat in the ctid & btree leaf linked lists make every lookup feel like table scans…!
Thankfully HOT (Heap-only Tuples) has saved us since. Virtually no dead tulles generated, and they get otherwise collected during regular ops like SELECT, amortizing cost over time, and preventing dangerous build up.
adilbasari about 3 hours ago |
We (the SpiceDB developers) took a similar approach to solve a different problem a few years ago: implementing strict serializability in Postgres[0]. By hooking into the transactions layer themselves (pg_xact), we could layer on our own MVCC reusing the real Postgres transactions to compute visibility and total ordering. When you can just tail the Postgres internals, you don't even need to implement a Postgres extension, which can keep it portable across locked-down, managed Postgres offerings.
Do folks know of other clever implementations of behavior by "spying" on the Postgres internals?
[0]: https://m.youtube.com/watch?v=_f6fHy4DWWM