From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: shm_mq_wait_internal gets stuck forever on fast shutdown |
Date: | 2017-08-21 14:07:29 |
Message-ID: | CAMsr+YESOO9dWW13F1vZS6_1e=4gMXP2BzVWcpqoRQn-xRErYA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 21 August 2017 at 21:44, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> While this would work, I don't really see the need for it given the
> availability of nonblocking operations. See mq_putmessage() for an
> example.
>
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.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Kumenkov | 2017-08-21 14:25:37 | Re: index-only count(*) for indexes supporting bitmap scans |
Previous Message | Robert Haas | 2017-08-21 13:44:00 | Re: shm_mq_wait_internal gets stuck forever on fast shutdown |