Why age (datfrozenxid) in postgres becomes 1073742202 not zero after each vacuum of database.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: <pgsql-performance@xxxxxxxxxxxxxx>, <pgsql-jobs@xxxxxxxxxxxxxx>, <pgsql-performance@xxxxxxxxxxxxxx>
Subject: Why age (datfrozenxid) in postgres becomes 1073742202 not zero after each vacuum of database.
From: "Brahma Prakash Tiwari" <brahma.tiwari@xxxxxxxxxxx>
Date: Thu, 12 Nov 2009 13:48:31 +0530
Thread-index: AcpjcLga9CR04LdiSnaR6X1MuYglmA==

Hi all

Why age (datfrozenxid) in postgres becomes 1073742202 not zero after vacuum of database.

Thanks in advance

Brahma Prakash Tiwari

DBA

Think before you print.|Go green

Follow-Ups:
- Re: Why age (datfrozenxid) in postgres becomes 1073742202 not zero after each vacuum of database.
  - From: Robert Haas

Prev by Date: Re: limiting performance impact of wal archiving.
Next by Date: Re: limiting performance impact of wal archiving.
Previous by thread: Adaptec Zero-Maintenance Cache Protection - Anyone using?
Next by thread: Re: Why age (datfrozenxid) in postgres becomes 1073742202 not zero after each vacuum of database.
Index(es):
- Date
- Thread

[Postgresql General] [Postgresql PHP] [PHP Users] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Yosemite]

Powered by Linux