Re: Refactor recovery conflict signaling a little

Heikki Linnakangas <hlinnaka@iki.fi>

From: Heikki Linnakangas <hlinnaka@iki.fi>

To: Chao Li <li.evan.chao@gmail.com>

Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2026-02-10T14:32:54Z

Lists: pgsql-hackers

On 03/02/2026 15:31, Heikki Linnakangas wrote:
> Attached are new versions of the remaining patches, with the above and 
> the typo and whitespace fixes that you pointed out.

I hear no objectons, so committed. Thanks for the review!

- Heikki

Commits

Don't clear pendingRecoveryConflicts at end of transaction
- 138592d1b066 19 (unreleased) landed
Refactor ProcessRecoveryConflictInterrupt for readability
- be5257725d7f 19 (unreleased) landed
Separate RecoveryConflictReasons from procsignals
- 17f51ea81875 19 (unreleased) landed
Use ProcNumber rather than pid in ReplicationSlot
- ddc3250208bd 19 (unreleased) landed
Don't hint that you can reconnect when the database is dropped
- 57bff90160fd 19 (unreleased) landed
Remove useless errdetail_abort()
- cd375d5b6d5f 19 (unreleased) landed
Teach standby conflict resolution to use SIGUSR1
- a8ce974cddef 9.0.0 cited