Re: HELP!!! The WAL Archive is taking up all space - Mailing list pgsql-general

From FattahRozzaq
Subject Re: HELP!!! The WAL Archive is taking up all space
Date
Msg-id CAKnA-A1G72Ai58L_vVy5abnA4nPj3gWk=wxS0b3yicK9=JiZVg@mail.gmail.com
Whole thread Raw
In response to Re: HELP!!! The WAL Archive is taking up all space  (John R Pierce <pierce@hogranch.com>)
Responses Re: HELP!!! The WAL Archive is taking up all space  (FattahRozzaq <ssoorruu@gmail.com>)
Re: HELP!!! The WAL Archive is taking up all space  (John R Pierce <pierce@hogranch.com>)
Re: HELP!!! The WAL Archive is taking up all space  (Adrian Klaver <adrian.klaver@aklaver.com>)
Re: HELP!!! The WAL Archive is taking up all space  (Andreas Kretschmer <andreas@a-kretschmer.de>)
List pgsql-general
Hi John,

I really don't know why I should keep the wal archives.
I implement streaming replication into 1 server (standby server).
I'm really newbie to PostgreSQL but the boss pushed me to handle it
and implement it in production f*&%*$%%$#%$#&# (forgive me)
They don't hire a database expert, I don't know why.

Hi Alan,
I have no problem with pg_xlog size which is only 67GB.
My issue is with the archive folder size.
I've read in this blog:
http://blog.endpoint.com/2014/09/pgxlog-disk-space-problem-on-postgres.html
And I change the archive_command into: archive_command = '/bin/true'
Is it a bad decision?

Hi Adrian,
Thank you very much for the suggestion. is pgarchivecleanup harmful?
Do you have a pgarchivecleanup example for my case?
How to run a dry-run?


Thank you,
Fattah


pgsql-general by date:

Previous
From: Edson Richter
Date:
Subject: Re: Overhead changing varchar(2000) to text
Next
From: FattahRozzaq
Date:
Subject: Re: HELP!!! The WAL Archive is taking up all space