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
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jobs pgsql-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

Browse pgsql-jobs by date

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

Browse pgsql-performance by date

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