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

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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Brahma Prakash Tiwari <brahma(dot)tiwari(at)inventum(dot)cc>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Why age (datfrozenxid) in postgres becomes 1073742202 not zero after each vacuum of database.
Date: 2009-11-13 21:05:38
Message-ID: 603c8f070911131305t1fc446fcw13df71b67da9093@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-jobspgsql-performance
[ removing -jobs from cc list as it is not appropriate for this posting ]

On Thu, Nov 12, 2009 at 3:18 AM, Brahma Prakash Tiwari
<brahma(dot)tiwari(at)inventum(dot)cc> wrote:
> Hi all
>
> Why age (datfrozenxid) in postgres becomes 1073742202 not zero after vacuum
> of database.
>
> Thanks in advance

I think you're misunderstanding the meaning of the column.  As the
fine manual explains:

"Similarly, the datfrozenxid column of a database's pg_database row is
a lower bound on the normal XIDs appearing in that database — it is
just the minimum of the per-table relfrozenxid values within the
database."

http://www.postgresql.org/docs/current/static/routine-vacuuming.html

...Robert

In response to

pgsql-jobs by date

Next:From: Megan MarioDate: 2009-11-17 20:27:02
Subject: PostgreSQL DBA opening, for post - thank you!
Previous:From: kirk BaillieDate: 2009-11-12 18:11:44
Subject: Contract Web Architect Opportunity in Portland, Oregon

pgsql-performance by date

Next:From: Greg SmithDate: 2009-11-13 21:06:20
Subject: Re: SSD + RAID
Previous:From: Fernando HeviaDate: 2009-11-13 20:57:38
Subject: Re: SSD + RAID

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