| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: Strange failure in LWLock on skink in REL9_5_STABLE |
| Date: | 2018-09-21 03:15:45 |
| Message-ID: | 26570.1537499745@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> writes:
> On Fri, Sep 21, 2018 at 2:59 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> 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.
> 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
Uh-huh.
https://www.postgresql.org/docs/devel/static/kernel-resources.html#SYSTEMD-REMOVEIPC
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-09-21 03:21:38 | Re: Strange failure in LWLock on skink in REL9_5_STABLE |
| Previous Message | Thomas Munro | 2018-09-21 03:11:04 | Re: Strange failure in LWLock on skink in REL9_5_STABLE |