Re: WAL FILES

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: "Gershon M(dot) Wolfe" <gary(dot)wolfe(at)lsbc(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WAL FILES
Date: 2002-01-08 23:10:40
Message-ID: Pine.LNX.4.30.0201081806260.725-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Gershon M. Wolfe writes:

> I am getting the following DEBUG message
>
> XLogWrite: new log file created - consider increasing WAL_FILES
>
> What would be a good number of files to shoot for, I am currently
> using the default. Some of my table are into the Gigabyte level.

This depends on the amount of data modification you do per transaction.

If the transaction that caused this message is a typical work load (and
not just a one-time bulk load, for instance) you can try to raise
WAL_FILES until the message goes away. I don't have a good formula at
hand, but basically WAL logs everything that you change during a
transaction.

You could perform a typical (long) transaction, hold off on the commit and
check the size of the accumulated logs under $PGDATA/pg_xlog.

--
Peter Eisentraut peter_e(at)gmx(dot)net

In response to

  • WAL FILES at 2002-01-08 20:03:09 from Gershon M. Wolfe

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-01-08 23:33:56 Re: Feature Request: DROP ALL FROM DATABASE database_name
Previous Message Peter Eisentraut 2002-01-08 22:59:23 ECPG warning