From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Alex Samad <alex(at)samad(dot)com(dot)au> |
Cc: | PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Begginers question |
Date: | 2017-08-16 06:16:51 |
Message-ID: | CAB7nPqTxrnNjOVqtaeYJZ=bTAMC7psApW5ciaVO3prQ=CC7=EQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Aug 16, 2017 at 2:32 PM, Alex Samad <alex(at)samad(dot)com(dot)au> wrote:
> 1) why did it fill up this time and not previously
> I add this
> archive_command = '/bin/true'
> wal_keep_segments = 1000 # <<< I'm guessing its this
>
> 2) how do I fix up, can I just remove the files from the pg_xlog directory
Don't do that. those files are managed by Postgres so you may finish
with a corrupted cluster. Instead you should lower the value of
wal_keep_segments, reload the server parameters, and then enforce two
checkpoints to force WAL segments to be recycled. Note that this
depends also on the values of checkpoint_segments
(max_wal_size/min_wal_size in Postgres 9.5 and onwards).
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | marin | 2017-08-16 09:51:09 | pg_column_size strange result... |
Previous Message | Alex Samad | 2017-08-16 05:41:57 | Re: cluster question |