Re: pg_clog question.

From: Chris Bowlby <chris(at)pgsql(dot)com>
To: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_clog question.
Date: 2004-04-27 19:26:45
Message-ID: 1083094005.588.28.camel@morpheus.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ahh, perfect, thank you..

On Tue, 2004-04-27 at 16:18, Alvaro Herrera wrote:
> On Tue, Apr 27, 2004 at 09:26:38AM -0300, Chris Bowlby wrote:
>
> > I've been noticing that files in the pg_clog directory test to stay
> > around forever, I know they are used to determine the state of
> > transaction id's, but according to the docs:
> >
> > "(However, the urgency of this concern has decreased greatly with the
> > adoption of a segmented storage method for pg_clog: it is no longer
> > necessary to keep old pg_clog entries around forever.)"
> >
> > How does one determine which files are no longer neccessary?
>
> You don't. They are deleted on VACUUM FULL when they are no longer
> needed.
>
> > Is the system configured to clear out stale ones during
> > startup/shutdown?
>
> No need to take the server down.
--
Chris Bowlby <chris(at)pgsql(dot)com>
PostgreSQL Inc.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2004-04-27 19:54:48 Re: Usability, MySQL, Postgresql.org, gborg, contrib,
Previous Message Alvaro Herrera 2004-04-27 19:12:36 Re: [HACKERS] What can we learn from MySQL?