Yes, absolutely! We would dump and reload all of our large databases in a
heartbeat if there were an option for a 64-bit xid!
Another quick question: When this database took itself offline to avoid
transaction id wraparound, we opted for a vacuum freeze in single-user mode.
Was that the right
Natalie Wenz writes:
> ... With the speed postgres is capable of, and the ever-falling prices
> of storage making larger, faster databases possible, has the possibility
> of changing the transaction id to a 64-bit (or even 128-bit!) value been
> considered?
Not terribly seriously --- the penaltie
Hi all,
I have a few questions related to recovering from a near-miss with
transactionid wraparound.
I'm currently running a vacuum freeze in single user mode on our largest
database (about 36 TB). It's been running for about 10 days (since the
database shut itself down to avoid xid wraparoun
