From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
To: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: [Slony1-general] WAL partition overloaded--by autovacuum?
Date: Wed, 07 Jul 2010 20:58:35 +1200
Message-ID: <4C3441BB.5020103@catalyst.net.nz> (raw)
In-Reply-To: <03D2C5F0-F222-4088-B5E4-8DA688565B70@iparadigms.com>
References: <03D2C5F0-F222-4088-B5E4-8DA688565B70@iparadigms.com>
On 07/07/10 13:10, Richard Yen wrote:
>
> This leads me to believe that there was a sudden flurry of write activity that occurred, and the process that would flush WAL files to /db/data/ couldn't keep up, thereby filling up the disk. I'm wondering if anyone else out there might be able to give me some insight or comments to my assessment--is it accurate? Any input would be helpful, and I'll try to make necessary architectural changes to keep this from happening again.
>
Do you have wal archiving enabled? (if so lets see your archive_command).
Cheers
Mark
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-performance@postgresql.org
Cc: mark.kirkwood@catalyst.net.nz
Subject: Re: [Slony1-general] WAL partition overloaded--by autovacuum?
In-Reply-To: <4C3441BB.5020103@catalyst.net.nz>
* 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