Skip site navigation (1) Skip section navigation (2)

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

From: "Brahma Prakash Tiwari" <brahma(dot)tiwari(at)inventum(dot)cc>
To: <pgsql-performance(at)postgresql(dot)org>,<pgsql-jobs(at)postgresql(dot)org>,<pgsql-performance(at)postgresql(dot)org>
Subject: Why age (datfrozenxid) in postgres becomes 1073742202 not zero after each vacuum of database.
Date: 2009-11-12 08:18:31
Message-ID: 20091112082006.416DD1D1445@quasar.inventum.in (view raw or flat)
Thread:
Lists: pgsql-jobspgsql-performance
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

 

Responses

pgsql-jobs by date

Next:From: kirk BaillieDate: 2009-11-12 18:11:44
Subject: Contract Web Architect Opportunity in Portland, Oregon
Previous:From: Ing . Marcos Luís Ortíz ValmasedaDate: 2009-11-12 06:04:53
Subject: Re: Why age (datfrozenxid) in postgres becomes 1073742202 not zero after each vacuum of database.

pgsql-performance by date

Next:From: Laurent LabordeDate: 2009-11-12 14:21:25
Subject: Re: limiting performance impact of wal archiving.
Previous:From: Greg SmithDate: 2009-11-12 06:47:35
Subject: Re: limiting performance impact of wal archiving.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group