| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Sergei Kornilov <sk(at)zsrv(dot)org>, Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Subject: | Re: Improve handling of parameter differences in physical replication |
| Date: | 2020-07-15 13:47:25 |
| Message-ID: | 5e93f9f5-9572-38d0-b740-f8a20dfcc165@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Here is a minimally updated new patch version to resolve a merge conflict.
On 2020-06-24 10:00, Peter Eisentraut wrote:
> Here is another stab at this subject.
>
> This is a much simplified variant: When encountering a parameter change
> in the WAL that is higher than the standby's current setting, we log a
> warning (instead of an error until now) and pause recovery. If you
> resume (unpause) recovery, the instance shuts down as before.
>
> This allows you to keep your standbys running for a bit (depending on
> lag requirements) and schedule the required restart more deliberately.
>
> I had previously suggested making this new behavior configurable, but
> there didn't seem to be much interest in that, so I have not included
> that there.
>
> The documentation changes are mostly carried over from previous patch
> versions (but adjusted for the actual behavior of the patch).
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| v4-0001-Replace-a-macro-by-a-function.patch | text/plain | 1.6 KB |
| v4-0002-Pause-recovery-for-insufficient-parameter-setting.patch | text/plain | 5.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jehan-Guillaume de Rorthais | 2020-07-15 13:52:20 | BUG #15285: Query used index over field with ICU collation in some cases wrongly return 0 rows |
| Previous Message | Tom Lane | 2020-07-15 13:45:54 | Re: renaming configure.in to configure.ac |