On 12/10/2026 10:14, Nitin Jadhav wrote:
The attached patch passes reachedConsistency through BackendStartupData, alongside canAcceptConnections, and uses the captured value when choosing the connection error detail. This only changes the reported DETAIL and HINT; connection acceptance and recovery behavior are unaffected.
That works. But what do you think of adding a new CAC_* code instead? It feels a bit weird to me that we've multiplexed CAC_NOTHOTSTANDBY for many different "sub-reasons".
- Heikki
