Re: [HACKERS] Weaker shmem interlock w/o postmaster.pid

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Daniel Gustafsson <daniel(at)yesql(dot)se>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, "9erthalion6(at)gmail(dot)com" <9erthalion6(at)gmail(dot)com>, "sfrost(at)snowman(dot)net" <sfrost(at)snowman(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] Weaker shmem interlock w/o postmaster.pid
Date: 2019-04-08 08:07:28
Message-ID: CA+hUKGKZncyFcQ95VQOXiTBPiyxhiJ-9YKTso=SHMQikyKhJyg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 8, 2019 at 6:42 PM Noah Misch <noah(at)leadboat(dot)com> wrote:
> - lorikeet's FailedAssertion("!(vmq->mq_sender == ((void *)0))" looked
> suspicious, but this happened six other times in the past year[2], always on
> v10 lorikeet.

It happens on v11 too:

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=lorikeet&dt=2018-09-25%2010%3A06%3A31

The text changed slightly because we dropped an unnecessary extra
pointer-to-volatile:

FailedAssertion("!(mq->mq_sender == ((void *)0))"

So either two workers started with the same parallel worker number, or
something unexpectedly overwrote the shm_mq struct?

--
Thomas Munro
https://enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2019-04-08 08:15:17 Re: reloption to prevent VACUUM from truncating empty pages at the end of relation
Previous Message Peter Eisentraut 2019-04-08 08:03:48 Re: pg_rewind vs superuser