From: | Alex Samad <alex(at)samad(dot)com(dot)au> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Begginers question |
Date: | 2017-08-16 10:46:31 |
Message-ID: | CAJ+Q1PVVeZmup1xDkM5=B=tgtk8JsHJGNqgYjZro-awRSi5C=Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 16 August 2017 at 16:16, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
wrote:
> 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
>
Too late, its okay its a learning experience.
> wal_keep_segments, reload the server parameters, and then enforce two
> checkpoints to force WAL segments to be recycled. Note that this
>
how do I force check points
> depends also on the values of checkpoint_segments
> (max_wal_size/min_wal_size in Postgres 9.5 and onwards).
> --
> Michael
>
thanks
From | Date | Subject | |
---|---|---|---|
Next Message | Achilleas Mantzios | 2017-08-16 10:55:17 | Re: Begginers question |
Previous Message | marin | 2017-08-16 09:51:09 | pg_column_size strange result... |