Re: prevent immature WAL streaming
От | Alvaro Herrera |
---|---|
Тема | Re: prevent immature WAL streaming |
Дата | |
Msg-id | 202109301432.mou5kmj3h2r6@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: prevent immature WAL streaming (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: prevent immature WAL streaming
|
Список | pgsql-hackers |
On 2021-Sep-30, Tom Lane wrote: > Andrew Dunstan <andrew@dunslane.net> writes: > > Regardless of this problem, I think we should simply call > > set_replication_conf unconditionally in init(). Replication connections > > are now allowed by default on Unix, this would just bring Windows nodes > > into line with that. > > Yeah, I was thinking along the same lines yesterday. The fact that > pre-commit testing failed to note the problem is exactly because we > have this random difference between what works by default on Unix > and what works by default on Windows. Let's close that gap before > it bites us again. +1 > There's still the issue of these tests overriding postgresql.conf > entries made by init(), but maybe we can live with that? I vote to at least have has_archiving=>1 set wal_level=replica, and potentially max_wal_senders=2 too (allows pg_basebackup). -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
В списке pgsql-hackers по дате отправления: