Re: "ERROR: latch already owned" on gharial

Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>

From: Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Thomas Munro <thomas.munro@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Noah Misch <noah@leadboat.com>, Andres Freund <andres@anarazel.de>, CM Team <cm@enterprisedb.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2022-07-13T03:30:10Z
Lists: pgsql-hackers
Thanks Robert.

We are receiving the alerts from buildfarm-admins for anole and gharial not
reporting. Who can help to stop these? Thanks

On Wed, Jul 6, 2022 at 1:27 AM Robert Haas <robertmhaas@gmail.com> wrote:

> On Sun, Jul 3, 2022 at 11:51 PM Thomas Munro <thomas.munro@gmail.com>
> wrote:
> > On Wed, Jun 1, 2022 at 12:55 AM Robert Haas <robertmhaas@gmail.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.
>
> I have commented out the BF stuff in crontab on that machine.
>
> --
> Robert Haas
> EDB: http://www.enterprisedb.com
>
>
>

-- 
Sandeep Thakkar

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Add debugging help in OwnLatch().

  2. Add barriers to the latch code.