| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Prabhjot Sheena <prabhjot(dot)sheena(at)rivalwatch(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>, Forums postgresql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: serious issue with age(relfrozenxid)::int. |
| Date: | 2014-07-20 15:28:26 |
| Message-ID: | 6699.1405870106@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
Prabhjot Sheena <prabhjot(dot)sheena(at)rivalwatch(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cassiano, Marco | 2014-07-21 09:27:00 | "ERROR: could not access status of transaction" (after upgrding from 9.3.2 to 9.3.4?) |
| Previous Message | Adrian Klaver | 2014-07-20 14:30:22 | Re: serious issue with age(relfrozenxid)::int. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-07-20 15:35:08 | Re: check database integrity |
| Previous Message | Adrian Klaver | 2014-07-20 14:30:22 | Re: serious issue with age(relfrozenxid)::int. |