Re: serious issue with age(relfrozenxid)::int. - Mailing list pgsql-general

From Adrian Klaver
Subject Re: serious issue with age(relfrozenxid)::int.
Date
Msg-id 53CBD27E.2000103@aklaver.com
Whole thread Raw
In response to Re: serious issue with age(relfrozenxid)::int.  (John R Pierce <pierce@hogranch.com>)
List pgsql-general
On 07/20/2014 01:05 AM, John R Pierce wrote:
> On 7/20/2014 12:29 AM, Prabhjot Sheena wrote:
>>           Most of my tables in postgresql database 8.3 is showing up
>> this. Pls suggest me what should be done with this and if this is
>> something really serious
>
> why are you casting age() to an int ?

My question would be why are you using age() on relfrozenxid?

 From here:

http://www.postgresql.org/docs/8.3/static/catalog-pg-class.html

relfrozenxid     xid           All transaction IDs before this one have been
replaced with a permanent ("frozen") transaction ID in this table. This
is used to track whether the table needs to be vacuumed in order to
prevent transaction ID wraparound or to allow pg_clog to be shrunk. Zero
(InvalidTransactionId) if the relation is not a table


 From here:

http://www.postgresql.org/docs/8.3/static/functions-datetime.html

age(timestamp)     interval     Subtract from current_date

So it is not surprising that it is not working.

>
>
>
>


--
Adrian Klaver
adrian.klaver@aklaver.com


pgsql-general by date:

Previous
From: Andrew Sullivan
Date:
Subject: Re: check database integrity
Next
From: Tom Lane
Date:
Subject: Re: serious issue with age(relfrozenxid)::int.