hi dave: A feature we used in pg admin 3 a fair bit was to terminate a rogue process — it was easy enough looking at the list of processes and clicking on one and hitting the terminate button.
why do we have rogue processes or things we want to kill — sometimes a customer may throw off a long running process a bunch of times which would kill performance of their machine … and it was highlighted in the list of processes with a different colour based on active, blocked, or what have you. in pgAdmin4, we have to refresh the list of sessions (curiously enough, thats ok .. in fact sometimes better than pgadmin 3 because the auto refresh could slow things down). what is missing are a couple of helpful things: - the state change and/or query start columns as options - and/or .. some sort of colour code on the row that shows long running queries - and the key request — a context menu item that would allow termination of the pid via pg_terminate_backend it would let us have a monitor on activity (the graphs are great) .. and a refresh to see who’s taking the cpu … and a way to kill the process — all on the dashboard. thanks again. and truly, the more I play, the more I appreciate what you have done. Doug Easterbrook Arts Management Systems Ltd. mailto:d...@artsman.com http://www.artsman.com Phone (403) 650-1978
signature.asc
Description: Message signed with OpenPGP using GPGMail
