Hi John, Really thanking you for spend time typing and responding my email. I think the archive_command returns success, I can see the archive directory piling up 16MB every 2 minutes. Maybe the pgarchivecleanup is the solution to cleanup the contents of archive folder? How to properly do it? What is the pgarchivecleanup example that I can use for this case? How to run a dry-run for pgarchivecleanup? Best Regards, FR On 10/12/2015, Joshua D. Drake <jd@xxxxxxxxxxxxxxxxx> wrote: > On 12/09/2015 04:38 PM, FattahRozzaq wrote: >> 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 :(( > > If the pg_xlog directory is growing it is likely that either: > > * wal_keep_segments is set high and your slave is not correctly > receiving updates. > > * You are using a replication slot and the slave is not correctly > receiving updates. > > If your archive_command does not return a success, your pg_xlog will > also grow but you don't need the archive_command *IF* your streaming > replication is working *UNLESS* you are also doing archiving or PITR. > > Sincerely, > > JD > > -- > Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564 > PostgreSQL Centered full stack support, consulting and development. > Announcing "I'm offended" is basically telling the world you can't > control your own emotions, so everyone else should do it for you. > -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
