| From: | FattahRozzaq <ssoorruu(at)gmail(dot)com> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: HELP!!! The WAL Archive is taking up all space |
| Date: | 2015-12-10 00:27:17 |
| Message-ID: | CAKnA-A1G72Ai58L_vVy5abnA4nPj3gWk=wxS0b3yicK9=JiZVg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | FattahRozzaq | 2015-12-10 00:38:51 | Re: HELP!!! The WAL Archive is taking up all space |
| Previous Message | Edson Richter | 2015-12-09 23:43:26 | Re: Overhead changing varchar(2000) to text |