Re: [GENERAL] pg_xlog on a hot_standby slave filling up - Mailing list pgsql-bugs

From Christoph Berg
Subject Re: [GENERAL] pg_xlog on a hot_standby slave filling up
Date
Msg-id 20150618105305.GA22374@msg.df7cb.de
Whole thread Raw
In response to Re: [GENERAL] pg_xlog on a hot_standby slave filling up  (Jeff Frost <jeff@pgexperts.com>)
Responses Re: [GENERAL] pg_xlog on a hot_standby slave filling up  (Christoph Berg <cb@df7cb.de>)
List pgsql-bugs
Re: Jeff Frost 2015-06-17 <AF73F62A-B83A-41A3-9CAA-CCFFDC4DB204@pgexperts.com>
> We thought it was related to the ssl renegotiation limit, but reducing it didn't seem to make it happen more often.
>
> The problem was that I couldn't seem to make a reproducible test case with pgbench and two servers, so it seems there
isslightly more at play.  
>
> I believe setting the ssl renegotiation limit to 0 made it stop. Can you confirm?

I've configured that, we'll see later today.

> Have you been able to reproduce synthetically?

No. I managed to make the test setup leak one file when the slave
server was restarted, but atm it doesn't reconnect/barf every 512MB.
I'm probably still missing some parameter. (sslcompression=0 was the
first I tried...)

Christoph
--
cb@df7cb.de | http://www.df7cb.de/

pgsql-bugs by date:

Previous
From: Guillaume Lelarge
Date:
Subject: Re: BUG #13450: problem about applying point-in-time recovery
Next
From: digoal@126.com
Date:
Subject: BUG #13453: PostgreSQL 9.5dev pgbench exponential distribution bug? (when threshold is small)