From: Tom Lane <tgl@sss.pgh.pa.us>
To: Prabhjot Sheena <prabhjot.sheena@rivalwatch.com>
cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>,
 Forums postgresql <pgsql-general@postgresql.org>
Subject: Re: serious issue with age(relfrozenxid)::int.
In-reply-to: 
 <CAOf_bQZtQzONb8=uekRJst+W3htRpD7qrW7E1BmAo0z4Gez40Q@mail.gmail.com>
References: 
 <CAOf_bQZtQzONb8=uekRJst+W3htRpD7qrW7E1BmAo0z4Gez40Q@mail.gmail.com>
Comments: In-reply-to Prabhjot Sheena <prabhjot.sheena@rivalwatch.com>
 message dated "Sun, 20 Jul 2014 00:29:13 -0700"
Date: Sun, 20 Jul 2014 11:28:26 -0400
Message-ID: <6699.1405870106@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-general-owner@postgresql.org

Prabhjot Sheena <prabhjot.sheena@rivalwatch.com> writes:
>           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

There's no reason to think that this means anything at all.  You did not
bother to filter by relkind, so most likely those MAXINT results
correspond to entries that have relfrozenxid = 0 because the system
doesn't track relfrozenxid for them (eg, indexes).

			regards, tom lane


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