Re: Improve handling of parameter differences in physical replication

From: Sergei Kornilov <sk(at)zsrv(dot)org>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Improve handling of parameter differences in physical replication
Date: 2020-02-27 09:48:14
Message-ID: 2392861582796894@myt6-4d759d962265.qloud-c.yandex.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello

Thank you for working on this!

> Where this becomes a serious problem is if you have many standbys and you do a failover.

+1
Several times my team would like to pause recovery instead of panic after change settings on primary. (same thing for create_tablespace_directories replay errors too...)

We documented somewhere (excluding code) shutting down the standby immediately upon receipt of the parameter change? doc/src/sgml/high-availability.sgml says only about "refuse to start".

regards, Sergei

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2020-02-27 10:13:54 Re: Improve handling of parameter differences in physical replication
Previous Message Peter Eisentraut 2020-02-27 09:43:50 Re: [Proposal] Level4 Warnings show many shadow vars