| From: | Christoph Berg <cb(at)df7cb(dot)de> |
|---|---|
| To: | Jeff Frost <jeff(at)pgexperts(dot)com> |
| Cc: | Xavier 12 <maniatux(at)gmail(dot)com>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] pg_xlog on a hot_standby slave filling up |
| Date: | 2015-06-18 10:53:05 |
| Message-ID: | 20150618105305.GA22374@msg.df7cb.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-general |
Re: Jeff Frost 2015-06-17 <AF73F62A-B83A-41A3-9CAA-CCFFDC4DB204(at)pgexperts(dot)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 is slightly 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(at)df7cb(dot)de | http://www.df7cb.de/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergi Casbas | 2015-06-18 12:11:14 | Re: BUG #13444: psql can't recover a pg_dump. |
| Previous Message | Xavier 12 | 2015-06-18 07:17:01 | Re: pg_xlog on a hot_stanby slave |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2015-06-18 10:54:11 | Re: Select query regarding info |
| Previous Message | Simon Riggs | 2015-06-18 10:51:34 | Re: serialization failure why? |