Re: [GENERAL] pg_xlog on a hot_standby slave filling up

> On Jun 16, 2015, at 11:35 AM, Christoph Berg <cb(at)df7cb(dot)de> wrote:
>
> [moving to -bugs]
>
> Re: Xavier 12 2015-06-16 <CAMOV8iB3oRzC4f7UTzOwC2wT08do3voi+PGN07uJq+ayo9E=cQ(at)mail(dot)gmail(dot)com>
>> Hi everyone,
>>
>> Questions about pg_xlogs again...
>> I have two Postgresql 9.1 servers in a master/slave stream replication
>> (hot_standby).
>>
>> Psql01 (master) is backuped with Barman and pg_xlogs is correctly
>> purged (archive_command is used).
>>
>> Hower, Psql02 (slave) has a huge pg_xlog (951 files, 15G for 7 days
>> only, it keeps growing up until disk space is full). I have found
>> documentation and tutorials, mailing list, but I don't know what is
>> suitable for a Slave. Leads I've found :
>
> Hi,
>
> I have the same problem here. Master/slave running on 9.3.current. On
> the master everything is normal, but on the slave server, files in
> pg_xlog and archive_status pile up. Interestingly, the filenames are
> mostly 0x20 apart. (IRC user Kassandry is reporting the same issue on
> 9.4 as well, including the 0x20 spacing.)

I’ve seen this before, but haven’t been able to make a reproducible test case yet.

Are you by chance using SSL to talk to the primary server? Is the ssl_renegotiation_limit the default of 512MB? 32 WAL files at 16MB each = 512MB. I found that it would always leave the WAL file from before the invalid record length message. Does that seem to be the case for you as well?