From: chris kim <chrisk@propaas.com>
To: Joshua D. Drake <jd@commandprompt.com>
To: pgsql-admin@postgresql.org
Subject: Re: Standby wal issue
Date: Mon, 6 Nov 2017 15:39:53 -0700
Message-ID: <8e33df50-415d-6336-e26f-59d213a5ea9e@propaas.com> (raw)
In-Reply-To: <4bc00717-c926-675f-b826-40f3324ce4fd@commandprompt.com>
References: <2e665cd4-da55-ae82-bdb7-c26e7ba91547@propaas.com>
<4bc00717-c926-675f-b826-40f3324ce4fd@commandprompt.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: chrisk@propaas.com, jd@commandprompt.com
Subject: Re: Standby wal issue
In-Reply-To: <8e33df50-415d-6336-e26f-59d213a5ea9e@propaas.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox