On 12/20/16 10:20 PM, Craig Ringer wrote:
> Tools look at pg_class.relfrozenxid and pg_databse.datfrozenxid more
> than probably anything else, so making changes that ignores them is
> pretty pointless.
Except the only useful way I know of to access *frozenxid is using
age(), and even that is a royal PITA when the xid is a special xid. So
I'd argue that we should effectively remove xid from user's view. Even
if we don't want to bloat pg_class by 4 bytes, we should just make xid
even more opaque than it is today and tell users to just cast it to bigxid.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
