| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Robins Tharakan <tharakan(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Sam James <sam(at)gentoo(dot)org>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Build failure with GCC 15 (defaults to -std=gnu23) |
| Date: | 2024-12-19 02:45:47 |
| Message-ID: | CA+hUKG+-FLH3B0TTfcvAY54u_sidgGGMV2b6tZiCu9d=NQ3vrw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sun, Dec 15, 2024 at 8:04 PM Robins Tharakan <tharakan(at)gmail(dot)com> wrote:
> [unexplained failure on alligator]
2024-12-19 12:38:26.223 ACDT [1956030:2] [unknown] FATAL: could not
open shared memory segment "/PostgreSQL.2167569412": No such file or
directory
That smells like systemd's RemoteIPC feature:
https://www.postgresql.org/docs/current/kernel-resources.html#SYSTEMD-REMOVEIPC
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2024-12-19 15:44:05 | Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows |
| Previous Message | Tom Lane | 2024-12-18 15:13:04 | Re: Not able to restore database - error: could not decompress data: Allocation error : not enough memory |