Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] shm_mq_wait_internal gets stuck forever on fast shutdown - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] shm_mq_wait_internal gets stuck forever on fast shutdown
Date
Msg-id CA+TgmoYXoZ=1Q_O2=j3smkbzVV3rVRfh8iDryt-bKdeSuev8pg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] shm_mq_wait_internal gets stuck forever on fast shutdown  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
Tree view 
On Mon, Aug 21, 2017 at 10:07 AM, Craig Ringer <craig@2ndquadrant.com> wrote:
> Makes sense, and I'm not especially concerned. If the expected solution to
> such usage is to use non-blocking calls, that's fine with me.
>
> I partly wanted to put this out there to help the next person looking into
> it. Or myself, when I've forgotten and go looking again ;) . But also, to
> ensure that this was in fact fully expected behaviour not an oversight re
> applying shm_mq to non-bgworker endpoints.

Yep, it's expected.  It's possible I should have designed it
differently, so if someone does feel concerned at some point we can
certainly debate how to change things, but what you're describing
matches my expectations and it seems OK to me, pretty much.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Alexander Kumenkov
Date:
Subject: Re: [HACKERS] index-only count(*) for indexes supporting bitmap scans
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Re: ICU collation variant keywords and pg_collationentries (Was: [BUGS] Crash report for some ICU-52 (debian8) COLLATE andwork_mem values)