Message-ID: <53CBD27E.2000103@aklaver.com>
Date: Sun, 20 Jul 2014 07:30:22 -0700
From: Adrian Klaver <adrian.klaver@aklaver.com>
User-Agent: Mozilla/5.0 (X11; Linux i686;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: John R Pierce <pierce@hogranch.com>, pgsql-general@postgresql.org
Subject: Re: serious issue with age(relfrozenxid)::int.
References: 
 <CAOf_bQZtQzONb8=uekRJst+W3htRpD7qrW7E1BmAo0z4Gez40Q@mail.gmail.com>
 <53CB7857.2060800@hogranch.com>
In-Reply-To: <53CB7857.2060800@hogranch.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-general-owner@postgresql.org

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


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general