Re: serious issue with age(relfrozenxid)::int.

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: John R Pierce <pierce(at)hogranch(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: serious issue with age(relfrozenxid)::int.
Date: 2014-07-20 14:30:22
Message-ID: 53CBD27E.2000103@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin 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(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2014-07-20 15:28:26 Re: serious issue with age(relfrozenxid)::int.
Previous Message John R Pierce 2014-07-20 08:05:43 Re: serious issue with age(relfrozenxid)::int.

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2014-07-20 15:28:26 Re: serious issue with age(relfrozenxid)::int.
Previous Message Andrew Sullivan 2014-07-20 14:02:42 Re: check database integrity