From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Noah Misch <noah(at)leadboat(dot)com>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, Peter Geoghegan <pg(at)bowt(dot)ie>, Andres Freund <andres(at)anarazel(dot)de> |
Subject: | Re: conchuela timeouts since 2021-10-09 system upgrade |
Date: | 2021-10-26 20:45:38 |
Message-ID: | CA+hUKGJ6XV1D9+L+VK7FLs=4a_mWcZHdNeiVA-o-Z_4T5dCLoQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Oct 27, 2021 at 3:29 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> [...] I'd be prepared to believe that prairiedog's
> ancient macOS version has some weird bug preventing kevent() from noticing
> available data ... but (a) surely conchuela wouldn't share such a bug,
> and (b) we've been using kevent() for a couple years now, so how come
> we didn't see this before?
There was this case soon after our kqueue support landed:
There are a few discussions on the 'net about the flakiness of both
kevent() and poll() around that vintage of macOS (both were new and
shared infrastructure, separate from select()); for example in libcurl
and libevent talked about this and blocked version ranges.
I don't have any ideas about conchuela. For the next person who
manages to reproduce this, just to sanity-check what we're passing in
to kevent(), what do *port and waitfor look like when secure_read()
blocks in WaitEventSetWait? It's good news that Andrey could
reproduce this on a VM. I may look into setting one of those up too.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2021-10-26 22:23:49 | Re: BUG #17245: Index corruption involving deduplicated entries |
Previous Message | Peter Geoghegan | 2021-10-26 20:36:25 | Re: BUG #17245: Index corruption involving deduplicated entries |