| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, tgl(at)sss(dot)pgh(dot)pa(dot)us, pg(at)bowt(dot)ie, pgsql-hackers(at)lists(dot)postgresql(dot)org, craig(dot)ringer(at)enterprisedb(dot)com, robertmhaas(at)gmail(dot)com |
| Subject: | Re: 011_crash_recovery.pl intermittently fails |
| Date: | 2023-01-25 00:20:39 |
| Message-ID: | CA+hUKGK4k1_zxRz6G+gyOCLQBxm8O3T_PCQa8x7yd+DVCWoqVA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 25, 2023 at 1:02 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> Well, this host has a problem, for what looks like a kernel issue, I
> guess.. This is repeatable across all the branches, randomly, with
> various errors with the POSIX DSM implementation:
> # [63cf68b7.5e5a:1] ERROR: could not open shared memory segment "/PostgreSQL.543738922": No such file or directory
> # [63cf68b7.5e58:6] ERROR: could not open shared memory segment "/PostgreSQL.543738922": No such file or directory
Something to do with
https://www.postgresql.org/docs/current/kernel-resources.html#SYSTEMD-REMOVEIPC
?
The failure I saw looked like a straight up case of the bug reported
in this thread to me.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2023-01-25 00:34:43 | Re: 011_crash_recovery.pl intermittently fails |
| Previous Message | Kyotaro Horiguchi | 2023-01-25 00:11:51 | Re: Time delayed LR (WAS Re: logical replication restrictions) |