Re: [Slony1-general] WAL partition overloaded--by autovacuum? - Mailing list pgsql-performance

From Kevin Grittner
Subject Re: [Slony1-general] WAL partition overloaded--by autovacuum?
Date
Msg-id 4C35DADF020000250003326D@gw.wicourts.gov
Whole thread Raw
In response to Re: [Slony1-general] WAL partition overloaded--by autovacuum?  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [Slony1-general] WAL partition overloaded--by autovacuum?  (Richard Yen <richyen@iparadigms.com>)
Re: [Slony1-general] WAL partition overloaded--by autovacuum?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
Robert Haas <robertmhaas@gmail.com> wrote:

> I don't understand how you managed to fill up 37GB of disk with
> WAL files.  Every time you fill up checkpoint_segments * 16MB of
> WAL files, you ought to get a checkpoint.  When it's complete, WAL
> segments completely written before the start of the checkpoint
> should be recyclable.  Unless I'm confused, which apparently I am.

You're not alone.  At first I was assuming that it was because of
archiving, but the OP says that's turned off.  Unless it had been on
and there wasn't a *restart* after changing the configuration, I
can't see how this could happen, and was hoping someone else could
cast some light on the issue.

The one setting that gave me pause was:

commit_siblings=200

but it doesn't seem like that should matter with:

commit_delay=0;

-Kevin

pgsql-performance by date:

Previous
From: Robert Haas
Date:
Subject: Re: [Slony1-general] WAL partition overloaded--by autovacuum?
Next
From: Jochen Erwied
Date:
Subject: Re: performance on new linux box