Re: Improve handling of parameter differences in physical replication - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Improve handling of parameter differences in physical replication
Date
Msg-id ddd72267-d4cb-4b4e-07af-4685316a2c92@2ndquadrant.com
Whole thread Raw
In response to Re: Improve handling of parameter differences in physical replication  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Improve handling of parameter differences in physical replication  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
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

pgsql-hackers by date:

Previous
From: Takashi Menjo
Date:
Subject: RE: [PoC] Non-volatile WAL buffer
Next
From: Bharath Rupireddy
Date:
Subject: Re: Parallel copy