[pgsql-jobs] 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]

Subject: [pgsql-jobs] 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

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: [pgsql-jobs] Why age (datfrozenxid) in postgres becomes 1073742202 not zero after each vacuum of database.
  - From: "Ing . Marcos Luís Ortíz Valmaseda"

Prev by Date: [pgsql-jobs] PostgreSQL expert (remote)
Next by Date: Re: [pgsql-jobs] Why age (datfrozenxid) in postgres becomes 1073742202 not zero after each vacuum of database.
Previous by thread: [pgsql-jobs] PostgreSQL expert (remote)
Next by thread: Re: [pgsql-jobs] Why age (datfrozenxid) in postgres becomes 1073742202 not zero after each vacuum of database.
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Home] [Postgresql General] [Postgresql Performance] [Postgresql Admin] [PHP Users] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Databases] [Yosemite Forum]

Powered by Linux