Re: Change behavior of (m)xid_age - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: Change behavior of (m)xid_age
Date
Msg-id 562969D2.7030608@BlueTreble.com
Whole thread Raw
In response to Re: Change behavior of (m)xid_age  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Change behavior of (m)xid_age  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 10/22/15 5:07 PM, Robert Haas wrote:
> On Thu, Oct 22, 2015 at 5:51 PM, Jim Nasby<Jim.Nasby@bluetreble.com>  wrote:
>> >It's also a permanent ID when the relation is first created.
> No it isn't.

Is there no case where it can be a permanent XID for a table or toast table?

The other issue is relminmxid, which if you're looking at relfrozenxid 
you'd want to look at as well. So you can't do a simple WHERE here.

Perhaps a better way to handle this is to just add correctly computed 
age fields to pg_stat_all_tables and pg_stat_database.
-- 
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



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Avoid full page images in streaming replication?
Next
From: Jim Nasby
Date:
Subject: Re: Avoid full page images in streaming replication?