Re: archive_cleanup_command when is called?

2014/1/15 Sameer Kumar <sameer(dot)kumar(at)ashnik(dot)com>

>
> the archive command is a cp command: 'test ! -f
>> /bigpart/local/incoming/%f && cp %p /bigpart/local/incoming/%f && chmod
>> a+rx /bigpart/local/incoming/%f'
>
>
> Your primary and secondary instances/db clusters are on the same server?
>
No, two servers: the temp partition (/bigpart/local/incoming) is on the
master and is shared via NFS to the standby (/mnt/db1_incoming_wals). On
the standby server the partition is mounted in rw mode and the postgres
user can read and write (and delete) on the partition (verified now).

>
> I modified the command in the recovery.conf as follow, but no changes and
>> no entry in the log file: archive_cleanup_command =
>> '/usr/pgsql-9.3/bin/pg_archivecleanup /mnt/db1_incoming_wals %r
>> 2>>/tmp/archive_cleanup.log'
>>
>
> Can you share your restore_command?
>
restore_command = 'cp /mnt/db1_incoming_wals/%f %p'

> Also share anything unusual that you notice in your database log files [on
> both the instances]
>
I will check again, but no logs I found about it, maybe I need to enable in
postgres.conf some logs details.

>
>
> Best Regards,
> *Sameer Kumar | Database Consultant*
>
> *ASHNIK PTE. LTD.*101 Cecil Street, #11-11 Tong Eng Building, Singapore
> 069533
> M : *+65 8110 0350 <%2B65%208110%200350>* T: +65 6438 3504 |
> www.ashnik.com
> www.facebook.com/ashnikbiz | www.twitter.com/ashnikbiz
>
> [image: email patch]
>
> This email may contain confidential, privileged or copyright material and
> is solely for the use of the intended recipient(s).
>