Re: Trimming transaction logs after extended WAL archive failures

Поиск
Список
Период
Сортировка
От Adrian Klaver
Тема Re: Trimming transaction logs after extended WAL archive failures
Дата
Msg-id 53324273.5060106@aklaver.com
обсуждение исходный текст
Ответ на Re: Trimming transaction logs after extended WAL archive failures  (Steven Schlansker <steven@likeness.com>)
Ответы Re: Trimming transaction logs after extended WAL archive failures  (Steven Schlansker <steven@likeness.com>)
Список 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
thanit saved space, and (I assume) the archiver fell behind and that was the source of the growing log.  There haven’t
beenany 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.klaver@aklaver.com


В списке pgsql-general по дате отправления:

Предыдущее
От: Jeff Janes
Дата:
Сообщение: Re: Trimming transaction logs after extended WAL archive failures
Следующее
От: Zenaan Harkness
Дата:
Сообщение: Re: Disk Encryption in Production