| From: | "Simone G(dot)" <simonedevs(at)gmail(dot)com> |
|---|---|
| To: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: ClientRead on ROLLABACK |
| Date: | 2024-06-27 15:34:50 |
| Message-ID: | 0F3BC6D3-65A6-445C-849C-B836A918E141@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Oh, I see. So the ROLLBACK command was executed! So I suppose the client was waiting just for the ACK and the connection has been left open.
> I think this is a super common confusion among users. Maybe we should
> consider making it clearer that no query is currently being executed.
> Something like
>
> IDLE: last query: SELECT * FROM mytable;
I think the clearest option would be leave the query column empty and add a new column last_query. But this suggestion may still do its job in clarifying that the query is not running.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marthin Laubscher | 2024-06-27 15:49:08 | Re: Custom type's modifiers |
| Previous Message | Jelte Fennema-Nio | 2024-06-27 15:26:02 | Re: ClientRead on ROLLABACK |