On Fri, Sep 21, 2018 at 2:59 PM Tom Lane <t...@sss.pgh.pa.us> wrote: > Thomas Munro <thomas.mu...@enterprisedb.com> writes: > > Andres pinged me off-list to point out this failure after my commit > > fb389498be: > > > ! FATAL: semop(id=332464133) failed: Invalid argument > > I was just looking at that, and my guess is that it was caused by > something doing an ipcrm or equivalent, and is unrelated to your patch. > Especially since skink has succeeded with that patch in several other > branches. > > If it's repeatable, then it would be time to get excited.
I found this case from January: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2018-01-05%2000%3A10%3A03 ! FATAL: semop(id=1313210374) failed: Invalid argument ! LINE 1: CREATE TABLE as_select1 AS SELECT * FROM pg_class WHERE relk... EINVAL The semaphore set doesn't exist, or semid is less than zero, or nsops has a nonpositive value. -- Thomas Munro http://www.enterprisedb.com
