Re: Trimming transaction logs after extended WAL archive failures

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Steven Schlansker <steven(at)likeness(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org postgresql" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Trimming transaction logs after extended WAL archive failures
Date: 2014-03-26 02:58:59
Message-ID: 53324273.5060106@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 03/25/2014 04:52 PM, Steven Schlansker wrote:
>

>> Some more questions, what happens when things begin to dawn on me:)
>>
>> You said the disk filled up entirely with log files yet currently the number(size) of logs is growing.
>
> It’s holding stable now. I tried to vacuum up to clean some space which turned out to generate more pg_xlog activity than it saved space, and (I assume) the archiver fell behind and that was the source of the growing log. There haven’t been any new segments since I stopped doing that.

Yea, vacuum just marks space as available for reuse it does not actually
free space.

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Zenaan Harkness 2014-03-26 03:06:00 Re: Disk Encryption in Production
Previous Message Jeff Janes 2014-03-26 01:33:03 Re: Trimming transaction logs after extended WAL archive failures