From: | Richard Yen <dba(at)richyen(dot)com> |
---|---|
To: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
Cc: | pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: [Slony1-general] WAL partition overloaded--by autovacuum? |
Date: | 2010-07-07 16:39:11 |
Message-ID: | 628D29CA-4776-422A-A9D5-9854F480CE43@richyen.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Sorry, I forgot to mention that archive_mode is "off" and commented out, and archive command is '' and commented out.
Thanks for following up!
-- Richard
On Jul 7, 2010, at 1:58, Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> wrote:
> 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
>
> --
> Sent via pgsql-performance mailing list (pgsql-performance(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
From | Date | Subject | |
---|---|---|---|
Next Message | Eliot Gable | 2010-07-07 19:23:12 | Re: Highly Efficient Custom Sorting |
Previous Message | Bruce Momjian | 2010-07-07 14:42:55 | Re: Weird XFS WAL problem |