Re: Large pg_xlog

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Francisco Reyes <lists(at)natserv(dot)net>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Large pg_xlog
Date: 2016-09-27 01:05:59
Message-ID: CAB7nPqSQxRby50oD7rkn5oR93KbOqmcoiu86GtP4hTR8-Vzs=A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Sep 27, 2016 at 9:26 AM, Francisco Reyes <lists(at)natserv(dot)net> wrote:
> The only times archive command failed I believe is because the volume where
> pg_xlog is ran out of space.
> FATAL: archive command was terminated by signal 3: Quit
>
> There are 2 of those today. So that does not seem to be the cause.

What are the files in pg_xlog/archive_status? Do see a lot of .ready
entries? Perhaps you could de-bloat things by using archive_command =
'/bin/true' (REM on Windows as far as I recall).
--
Michael

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Paquier 2016-09-27 02:57:31 Re: Replication slot on master failure
Previous Message Francisco Reyes 2016-09-27 00:26:09 Re: Large pg_xlog