On Sun, Jan 19, 2025 at 3:55 AM Tom Lane wrote:
>
> One idea that seems like it could be safe is to change the prompt,
> so that your experience could be like
>
> postgres=# SELECT foo, bar, baz,
> -# (uh-oh)
>
> This only helps for people who are entering multi-line SQL,
+1,will look into it.
On Sun, Dec 8, 2024 at 4:31 AM Tomas Vondra wrote:
>
> Yes, it's true that if the connection breaks, the client may not notice
> that until the next command. But why would we want to kill psql in that
> case? How does that improve the user experience?
>
>
Hi Tomas,sorry for the (very!) late reply
I wrote:
> Anyway, I'm inclined to close this CF entry as returned-with-feedback.
> Perhaps there's something we can do here, but the current patch feels
> like a dead end.
Also, the submitter seems to have disappeared:
- The following addresses had permanent fatal errors -
(reas
Tomas Vondra writes:
> Yes, it's true that if the connection breaks, the client may not notice
> that until the next command. But why would we want to kill psql in that
> case? How does that improve the user experience?
> If you're in an interactive session (which is where this matters), and
> yo
On 11/8/24 19:42, Srinath Reddy Sadipiralla wrote:
> Hi ,
>
> When a user tries to enter a large query, thinking the server is still
> running, and to their surprise, they discover that the server has
> crashed or stopped, I have observed that the psql process will still be
> running if it is idle
Hi ,
When a user tries to enter a large query, thinking the server is still running,
and to their surprise, they discover that the server has crashed or stopped, I
have observed that the psql process will still be running if it is idle even
after the server crashes or stops.
solved this
