Re: `pg_ctl init` crashes when run concurrently; semget(2) suspected
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Gavin Panella <gavinpanella@gmail.com>
Cc: pgsql-hackers@postgresql.org
Date: 2025-08-11T15:12:17Z
Lists: pgsql-hackers
Attachments
- cope-with-EINVAL-from-semget.patch (text/x-diff) patch
I wrote: > My first thought about fixing it is to go ahead and retry after > EINVAL, but keep a count of failures, and give up after 100 or 1000 > or so. This'd be safer in any case --- it's not really great that > IpcSemaphoreCreate is willing to retry an infinite number of times. Concretely, about like the attached. I don't have any clear idea about what loop limit to use, but I think we do need one. regards, tom lane
Commits
-
Don't treat EINVAL from semget() as a hard failure.
- 21fddb3d7690 19 (unreleased) landed
- f4c0883448d8 15.15 landed
- e67d5f7baa7d 16.11 landed
- e3b3fa863810 13.23 landed
- b3d6e8b63bc1 14.20 landed
- ab92f0e7f7d7 17.7 landed
- 787cd2b7d5cd 18.0 landed
-
Give up on running with NetBSD/OpenBSD's default semaphore settings.
- 810a8b1c8051 18.0 cited