| From: | chris kim <chrisk(at)propaas(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Standby wal issue |
| Date: | 2017-11-06 22:39:53 |
| Message-ID: | 8e33df50-415d-6336-e26f-59d213a5ea9e@propaas.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-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
>>
>>
>>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PropAAS DBA | 2017-11-07 01:10:14 | ERROR: invalid byte sequence for encoding "UTF8": 0x00 |
| Previous Message | Joshua D. Drake | 2017-11-06 21:22:26 | Re: Standby wal issue |