From: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Begginers question |
Date: | 2017-08-16 10:55:17 |
Message-ID: | 5c025255-5e48-7b2e-7dec-37c5b939cf66@matrix.gatewaynet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 16/08/2017 13:46, Alex Samad wrote:
>
>
> On 16 August 2017 at 16:16, Michael Paquier <michael(dot)paquier(at)gmail(dot)com <mailto: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 <mailto: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
checkpoint ;
(the ; is not meant as a smiley or whatever )
>
> depends also on the values of checkpoint_segments
> (max_wal_size/min_wal_size in Postgres 9.5 and onwards).
> --
> Michael
>
>
> thanks
--
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt
From | Date | Subject | |
---|---|---|---|
Next Message | gmb | 2017-08-16 12:41:26 | optimize pg_tables query ( text vs varchar ) ...why ? |
Previous Message | Alex Samad | 2017-08-16 10:46:31 | Re: Begginers question |