From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | kimon(dot)krenz(at)part9(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #16832: Interrupted system call when working with large data tables |
Date: | 2021-01-22 17:24:00 |
Message-ID: | 20210122172400.eiao4kgzhhpmtb5y@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi,
On 2021-01-21 22:16:55 +0000, PG Bug reporting form wrote:
> I've recently updated macOS to Big Sur, and simultaneously to PostgreSQL
> 13.1.
> Since these updates PostgreSQL keeps throwing 'Interrupted system call'
> errors in three instances, which produce similar 'could not open file
> pg_wal/" errors (see below 1.,2. and 3.).
> The problem might be linked to BUG #16827: macOS interrupted syscall leads
> to a crash.
There is additional information in another bug report at
https://postgr.es/m/16827-7606aeb21d38c228%40postgresql.org
I don't really know what to do here short term - adding EINTR handling
to syscalls that traditionally never had returned EINTR (which used to
only happen for "blocking" system calls) will be a fair amount of work.
I'll also respond in the other thread, CCing you, as there's more
information there.
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2021-01-22 17:35:35 | Re: BUG #16827: macOS interrupted syscall leads to a crash |
Previous Message | Alex F | 2021-01-22 17:21:10 | Re: BUG #16833: postgresql 13.1 process crash every hour |