3 ms·
> txid wraparound from vacuum failures probably being the most common Hopefully OrioleDB can upstream all the necessary changes soon. For those who don't know,
by orthoxerox 2y ago
> txid wraparound from vacuum failures probably being the most common
Hopefully OrioleDB can upstream all the necessary changes soon. For those who don't know, it's a storage engine for Postgres that uses undo logs instead of vacuuming old records.
- oliverrice 2y agoOrioleDB maintains a very small set of Postgres patches that are targeted for upstream. The storage engine that mitigates the need for vacuuming [1] is implemented in a standard Postgres extension, so that will still need to be installed by the Postgres host in order to take advantage of it. But yeah, looking forward to that day too! [1] https://www.orioledb.com/blog/no-more-vacuum-in-postgresql https://www.orioledb.com/blog/no-more-vacuum-in-postgresql