You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unable to quite pgcli if the server has shutdown. I can't seem to exit if I have a running pgcli against a server that has shutdown after I opened the connection.
Looks like this bug happens even when there are any kinds of network errors. Why do we need a connection to quit?
I'm connecting to a database behind a VPN, so this one time I allowed VPN to expire, losing the connection. So I stepped in this bug:
sync> select count(*) from segments;
consuming input failed: could not receive data from server: Can't assign requested address
SSL SYSCALL error: Can't assign requested address
Time: 55.661s (55 seconds), executed in: 55.660s (55 seconds)
sync> select count(*) from segments;
sending query failed: could not receive data from server: Can't assign requested address
SSL SYSCALL error: Can't assign requested address
another command is already in progress
Time: 0.002s
sync> select count(*) from segments;
sending query failed: could not receive data from server: Can't assign requested address
SSL SYSCALL error: Can't assign requested address
another command is already in progress
another command is already in progress
Time: 0.002s
sync> \q
A transaction is ongoing. Choose `c` to COMMIT, `r` to ROLLBACK, `a` to abort exit. [a]: ^[[A
A transaction is ongoing. Choose `c` to COMMIT, `r` to ROLLBACK, `a` to abort exit. [a]: r
sending query failed: could not receive data from server: Can't assign requested address
SSL SYSCALL error: Can't assign requested address
another command is already in progress
another command is already in progress
another command is already in progress
Time: 0.006s
sync> select count(*) from segments;
sending query failed: could not receive data from server: Can't assign requested address
SSL SYSCALL error: Can't assign requested address
another command is already in progress
another command is already in progress
another command is already in progress
another command is already in progress
Time: 0.001s
sync> \q
A transaction is ongoing. Choose `c` to COMMIT, `r` to ROLLBACK, `a` to abort exit. [a]: r
sending query failed: could not receive data from server: Can't assign requested address
SSL SYSCALL error: Can't assign requested address
another command is already in progress
another command is already in progress
another command is already in progress
another command is already in progress
another command is already in progress
Time: 0.003s
sync> \q
A transaction is ongoing. Choose `c` to COMMIT, `r` to ROLLBACK, `a` to abort exit. [a]: r
sending query failed: could not receive data from server: Can't assign requested address
SSL SYSCALL error: Can't assign requested address
another command is already in progress
another command is already in progress
another command is already in progress
another command is already in progress
another command is already in progress
another command is already in progress
Time: 0.002s
All three options(c, r, a) lead to the same result.
Activity
Zverik commentedon Aug 15, 2025
Looks like this bug happens even when there are any kinds of network errors. Why do we need a connection to quit?
I'm connecting to a database behind a VPN, so this one time I allowed VPN to expire, losing the connection. So I stepped in this bug:
All three options(c, r, a) lead to the same result.