On Wed, Jun 26, 2024 at 08:48:06AM +0200, Anthonin Bonnefoy wrote:
> Yeah, this happened last week on one of our replicas (version 15.5)
> last week that had 134 days uptime. We are doing a lot of parallel
> queries on this cluster so the combination of high uptime plus
> parallel workers creation eventually triggered the issue.
It is not surprising that it would take this much amount of time
before detecting it. I've applied the patch down to 15. Thanks a lot
for the analysis and the patch!
--
Michael
