Re: Missed condition-variable wakeups on FreeBSD

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Missed condition-variable wakeups on FreeBSD
Date: 2023-01-13 02:00:58
Message-ID: CA+hUKGLqiaWXf98=aLPANQQrrXx=n6BZdN+kjDod5YVAv5nEEg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Feb 27, 2022 at 8:07 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I have observed this three times in the REL_11 branch, once
> in REL_12, and a couple of times last summer before it occurred
> to me to start keeping notes. Over that time the machine has
> been running various patchlevels of FreeBSD 13.0.

FTR I noticed that my animal elver hadn't reported for a while and
logged and found it locked up, a bit like that, but in test_shm_mq
rather than PHJ. It's FreeBSD 13.1 on a fairly fast 16 way amd64 (in
a jail), and it was testing REL_12_STABLE, so using poll() for
WaitEventSetWaitBlock(). When I connected a debugger then
disconnected, it was unblocked and continued. Unfortunately I didn't
get any new information :-(

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2023-01-13 02:09:11 Re: [EXTERNAL] Re: [PATCH] Support using "all" for the db user in pg_ident.conf
Previous Message Amin 2023-01-13 01:52:21 Re: Get access to the whole query in CustomScan path callback