Re: "ERROR: latch already owned" on gharial

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Noah Misch <noah(at)leadboat(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, CM Team <cm(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: "ERROR: latch already owned" on gharial
Date: 2022-07-04 03:50:37
Message-ID: CA+hUKGL9XR+n2D_1RzUTavzwWvq5Wh69d3dy+DDTB=joPnDzww@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jun 1, 2022 at 12:55 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> OK, I have access to the box now. I guess I might as well leave the
> crontab jobs enabled until the next time this happens, since Thomas
> just took steps to improve the logging, but I do think these BF
> members are overdue to be killed off, and would like to do that as
> soon as it seems like a reasonable step to take.

A couple of months later, there has been no repeat of that error. I'd
happily forget about that and move on, if you want to decommission
these.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2022-07-04 03:52:58 Re: Handle infinite recursion in logical replication setup
Previous Message Michael Paquier 2022-07-04 03:01:28 Re: Too-long socket paths are breaking several buildfarm members