pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Richard Huxton <dev@archonet.com>
To: Florian Litot <flitot@besancon.sema.slb.com>
To: pgsql-general@postgresql.org
Subject: Re: log file?
Date: Tue, 5 Nov 2002 11:47:21 +0000
Message-ID: <200211051147.21164.dev@archonet.com> (raw)
In-Reply-To: <4.3.2.7.2.20021105121304.022c5100@pop.besancon.tt.slb.com>
References: <4.3.2.7.2.20021105095405.023e8910@pop.besancon.tt.slb.com>
	<4.3.2.7.2.20021105121304.022c5100@pop.besancon.tt.slb.com>

On Tuesday 05 Nov 2002 11:14 am, Florian Litot wrote:
> At 11:47 05/11/02, Richard Huxton wrote:
> >PG writes all transactions to disk before actually making changes so that
> > you can recover in the event of a crash. It splits this transaction log
> > into chunks and recycles them when all the transactions it refers to are
> > no longer of interest.
>
> but the problem is it never recycle this file so i have a got a px_log 2Go
> how i can resolve this problem?
> why it doesn't recycle?

According to the log you posted it was being recycled.

How many files are there in pg_xlog and what dates do they have?
What are the WAL settings in your postgresql.conf file?
Do you have any clients that have been running a long time?

-- 
  Richard Huxton



view thread (26+ messages)  latest in thread

Message-ID: <200211051147.21164.dev@archonet.com>
Permalink:  ../200211051147.21164.dev@archonet.com/
Also on:    postgresql.org/message-id/200211051147.21164.dev@archonet.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-general@postgresql.org
  Cc: dev@archonet.com, flitot@besancon.sema.slb.com
  Subject: Re: log file?
  In-Reply-To: <200211051147.21164.dev@archonet.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox