Re: Changing the setting of wal_sender_timeout per standby
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Michael Paquier <michael@paquier.xyz>,
"Tsunakawa,
Takayuki" <tsunakawa.takay@jp.fujitsu.com>,
"'Masahiko Sawada'" <sawada.mshk@gmail.com>,
Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>,
"pgsql-hackers@lists.postgresql.org"
<pgsql-hackers@lists.postgresql.org>
Date: 2018-09-23T14:47:44Z
Lists: pgsql-hackers
Andres Freund <andres@anarazel.de> writes: > Have there been discussions about the security effects of this change? > Previously the server admin could control the timeout, which could > affect things like syncrep, after this it's not possible anymore. I > *think* that's ok, but it should be discussed. Hm. An evil replication connection could already cause all sorts of operational problems (and I'm not counting grabbing all your data). Does this add anything much new in that line? It seems like the effects would be at least in the same ballpark as not sending hot-standby-feedback messages in a timely fashion. regards, tom lane
Commits
-
Make GUC wal_sender_timeout user-settable
- db361db2fce7 12.0 landed