Currently, interrupting martin or martin-cp (e.g., via Ctrl+C) stops the client process, but it does not terminate the corresponding active queries on the database side. Ideally, a client-side cancellation should propagate to PostgreSQL to stop and clean up the backend processes.
Reference:
This is similar to the behavior reported here: #6
cc: @nyurik
Currently, interrupting
martinormartin-cp(e.g., viaCtrl+C) stops the client process, but it does not terminate the corresponding active queries on the database side. Ideally, a client-side cancellation should propagate to PostgreSQL to stop and clean up the backend processes.Reference:
This is similar to the behavior reported here: #6
cc: @nyurik