Re: EINTR in ftruncate() - Mailing list pgsql-hackers

From Andres Freund
Subject Re: EINTR in ftruncate()
Date
Msg-id 20220701173016.mpt6n2yl5dyta7o6@alap3.anarazel.de
Whole thread Raw
In response to EINTR in ftruncate()  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: EINTR in ftruncate()
List pgsql-hackers
Hi,

On 2022-07-01 17:41:05 +0200, Alvaro Herrera wrote:
> Nicola Contu reported two years ago to pgsql-general[1] that they were
> having sporadic query failures, because EINTR is reported on some system
> call.  I have been told that the problem persists, though it is very
> infrequent.  I propose the attached patch.  Kyotaro proposed a slightly
> different patch which also protects write(), but I think that's not
> necessary.

What is the reason for the || ProcDiePending || QueryCancelPending bit? What
if there's dsm operations intentionally done while QueryCancelPending?

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?
Next
From: Andres Freund
Date:
Subject: Re: Issue with pg_stat_subscription_stats