From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Simone Giusso <simonedevs(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: ClientRead on ROLLABACK |
Date: | 2024-06-27 15:21:38 |
Message-ID: | 1735502.1719501698@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Simone Giusso <simonedevs(at)gmail(dot)com> writes:
> I have a question regarding postgresql waiting for the client. I queried
> the pg_stat_activity because I noticed a connection that had not been
> released for days!!! I saw that the wait_event was ClientRead and the query
> was ROLLBACK. What the server is waiting for from the client?
You are misunderstanding that display. If the wait state is ClientRead
then the server has nothing to do and is awaiting a fresh SQL command
from the client. The query that's shown is the last-executed query.
(We used to show "<IDLE>" in the query column in this state, but that
was deemed less helpful than the current behavior.)
> So I ended up in a situation where both client and server were reading from
> the socket :(. I'm not sure why. Something went wrong between client and
> server, network problems?
Yeah, a dropped packet could explain this perhaps.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jelte Fennema-Nio | 2024-06-27 15:26:02 | Re: ClientRead on ROLLABACK |
Previous Message | Tom Lane | 2024-06-27 15:06:27 | Re: Custom type's modifiers |