| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Change behavior of (m)xid_age |
| Date: | 2015-10-22 22:57:22 |
| Message-ID: | 562969D2.7030608@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/22/15 5:07 PM, Robert Haas wrote:
> On Thu, Oct 22, 2015 at 5:51 PM, Jim Nasby<Jim(dot)Nasby(at)bluetreble(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-10-22 22:59:06 | Re: Avoid full page images in streaming replication? |
| Previous Message | Alvaro Herrera | 2015-10-22 22:53:27 | Re: Avoid full page images in streaming replication? |