On Thu, 2020-03-12 at 01:16 +0000, Virendra Kumar wrote: > This is simple patch, would that impact badly if patched to prior versions or some other > constraints forced to not do that. I am just trying to understand this a bit. It is not that this patch would have a terrible impact. There is a good reason for being very strict about what to backport: we want users to install the latest minor release without them worrying if that will change any behavior they rely on or not. If the users are not confident that they can always install the latest minor release without extra testing, they won't install them and run old, buggy releases. This would be bad for PostgreSQL's reputation of being stable and reliable. So also "harmless" changes that don't actually fix a bug are not backported. > On AWS RDS we have primary and secondary hosts known in advance in most cases. > So if a primary instance fails over it will be other host and hence we have to > update the active nodes in targets using lamda function. AWS RDS fails over very > quickly under 3 seconds mostly and hence we have set that health checks to 3seconds. > I'll go back to AWS folks and see if they can do this in prior releases. Hm. A system that fails over withing three seconds seems fragile to me. Doesn't that mean that evvery little hiccup will cause a failover? Maybe I don't understand what you are doing, but wouldn't it be better to catch errors whenever you perform a database operation and retry the operation if the error indicates that you have lost the connection? Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com
