Quick information,
After I realize, the line "archive_command=/bin/true" is a bad
decision, I have revert it back.
Now I'm really confused and panic.
I don't know what to do, and I don't really understand the postgresql.conf
I'm a network engineer, I should handle the network and also
postgresql database.
Oh man, the office is so good but this part is sucks :((
--
On 10/12/2015, FattahRozzaq <ssoorruu@gmail.com> wrote:
> 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
>
