Subject: Re: Standby wal issue
To: "Joshua D. Drake" <jd@commandprompt.com>, pgsql-admin@postgresql.org
References: <2e665cd4-da55-ae82-bdb7-c26e7ba91547@propaas.com>
 <4bc00717-c926-675f-b826-40f3324ce4fd@commandprompt.com>
From: chris kim <chrisk@propaas.com>
Message-ID: <8e33df50-415d-6336-e26f-59d213a5ea9e@propaas.com>
Date: Mon, 6 Nov 2017 15:39:53 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <4bc00717-c926-675f-b826-40f3324ce4fd@commandprompt.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Thanks for helping. Here's the recovery.conf file:

standby_mode= 'on'
trigger_file = '/tmp/standby.trg'
archive_cleanup_command = '/usr/pgsql-9.2/bin/pg_archivecleanup 
/ComplianceDB/data/pg_xlog/ %r'


On 11/06/2017 02:22 PM, Joshua D. Drake wrote:
> On 11/06/2017 11:34 AM, chris kim wrote:
>> Hi Community,
>>
>> I have a standby server that is in replication mode only, and is 
>> storing an insane amount of wal files and it's only on the standby 
>> not the master. I have over 50,000 wal files right now. I only have a 
>> few processes running on the background and they all seem to not be 
>> the problem. This is running on postgres 9.2. Any help would be 
>> greatly appreciated.
>
> What does your recovery.conf file say?
>
> JD
>
>>
>>
>> Thanks,
>>
>> Chris
>>
>>
>>
>


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin