| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Benjamin Leis <benleis1(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Interpreting MessageQueueSend state |
| Date: | 2023-11-14 04:38:21 |
| Message-ID: | 0b7aba59f7b629f3fe7a46afdb174b7e5c08d880.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 2023-11-13 at 17:06 -0800, Benjamin Leis wrote:
> I'm looking at a pg_stat_activity dump where there are a group of active
> threads stuck for a long time in MessageQueueSend
> 7:52.394089+00 | IPC | MessageQueueSend | active |
> | 27406510 | -5892847938856697008 | SELECT ....
> Does this mean they are blocked on clients reading data or does it
> represent something blocking on the server side?
That's something on the server: a parallel worker process is waiting to
send data to the parallel leader process. Look for the "leader_pid" column
in the "pg_stat_activity" line above and see what that process is doing.
I wouldn't worry about a parellel worker in that state, as long as there
is no problem with the parallel leader.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shaik Mohammad Mujeeb | 2023-11-14 07:51:40 | Re: Issue in compiling postgres on latest macOS 14.1.1 |
| Previous Message | Benjamin Leis | 2023-11-14 01:06:04 | Interpreting MessageQueueSend state |