From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
---|---|
To: | nicola(dot)contu(at)gmail(dot)com |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, pgsql-general(at)lists(dot)postgresql(dot)org, Alessandro(dot)aste(at)gtt(dot)net |
Subject: | EINTR while resizing dsm segment. |
Date: | 2020-04-02 08:25:40 |
Message-ID: | 20200402.172540.1001501556479933332.horikyota.ntt@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
I provided the subject, and added -hackers.
> Hello,
> I am running postgres 11.5 and we were having issues with shared segments.
> So I increased the max_connection as suggested by you guys and reduced my
> work_mem to 600M.
>
> Right now instead, it is the second time I see this error :
>
> ERROR: could not resize shared memory segment "/PostgreSQL.2137675995" to
> 33624064 bytes: Interrupted system call
The function posix_fallocate is protected against EINTR.
| do
| {
| rc = posix_fallocate(fd, 0, size);
| } while (rc == EINTR && !(ProcDiePending || QueryCancelPending));
But not for ftruncate and write. Don't we need to protect them from
ENTRI as the attached?
--
Kyotaro Horiguchi
NTT Open Source Software Center
Attachment | Content-Type | Size |
---|---|---|
0001-Protect-dsm_impl-from-EINTR.patch | text/x-patch | 1.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2020-04-02 08:53:28 | Re: using a common key value on both sides of a union ? |
Previous Message | Silvio Fabi - NBS srl | 2020-04-02 08:12:53 | Re: postgres: archiver process failed on 000000010000020A00000073 |
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2020-04-02 08:30:35 | Re: WAL usage calculation patch |
Previous Message | Michael Paquier | 2020-04-02 08:03:36 | Re: pgbench - add \aset to store results of a combined query |