Re: Change behavior of (m)xid_age

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Change behavior of (m)xid_age
Date: 2015-10-22 23:25:06
Message-ID: CA+Tgmoau5wDW+qNo-N_4F+2B2cLNDyamxPmXg+vEh20mai1Feg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 22, 2015 at 6:57 PM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
> Is there no case where it can be a permanent XID for a table or toast table?

I don't think so.

> 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.

I don't really know what you're referring to here, but it doesn't sound serious.

> Perhaps a better way to handle this is to just add correctly computed age
> fields to pg_stat_all_tables and pg_stat_database.

I'll defer to others on that point.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2015-10-22 23:26:10 Re: Making tab-complete.c easier to maintain
Previous Message Andres Freund 2015-10-22 23:21:51 Re: Re: [BUGS] BUG #13611: test_postmaster_connection failed (Windows, listen_addresses = '0.0.0.0' or '::')