Re: vacuum freeze performance, wraparound issues - Mailing list pgsql-admin

From Tom Lane
Subject Re: vacuum freeze performance, wraparound issues
Date
Msg-id 5056.1376367324@sss.pgh.pa.us
Whole thread Raw
In response to vacuum freeze performance, wraparound issues  (Natalie Wenz <nataliewenz@ebureau.com>)
Responses Re: vacuum freeze performance, wraparound issues
List pgsql-admin
Natalie Wenz <nataliewenz@ebureau.com> 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 penalties from making row headers 8 bytes
bigger have always seemed to outweigh the advantages.  (128 bits is right
out; we don't even have 128-bit LSNs.)

We'd probably take a patch to make 64-bit XIDs available as a compile-time
option, if someone wanted to do the legwork to write and test it.  But
let me ask you this: if such an option existed, would you be willing to
dump and reload your database to take advantage of it?  The conversion
costs of changing row header format seem like they'd discourage exactly
those people whom such a feature could help.

            regards, tom lane


pgsql-admin by date:

Previous
From: Natalie Wenz
Date:
Subject: vacuum freeze performance, wraparound issues
Next
From: Scott Whitney
Date:
Subject: WTF? 9.2.4 Logs have the wrong day of the week?