Обсуждение: Pgadmin4: ability to terminate the backend process from the list of processes and highlight activity
Pgadmin4: ability to terminate the backend process from the list of processes and highlight activity
От
Doug Easterbrook
Дата:
<div class="">hi dave:</div><div class=""><br class="" /></div><div class="">A feature we used in pg admin 3 a fair bit wasto terminate a rogue process — it was easy enough looking at the list of processes and clicking on one and hitting theterminate button.</div><div class=""><br class="" /></div><div class="">why do we have rogue processes or things we wantto kill — sometimes a customer may throw off a long running process a bunch of times which would kill performance oftheir machine … and it was highlighted in the list of processes with a different colour based on active, blocked, or whathave you.</div><div class=""><br class="" /></div><div class=""><br class="" /></div><div class="">in pgAdmin4, we haveto refresh the list of sessions (curiously enough, thats ok .. in fact sometimes better than pgadmin 3 because the autorefresh could slow things down).</div><div class=""><br class="" /></div><div class=""><br class="" /></div><div class="">whatis missing are a couple of helpful things:</div><div class="">- the state change and/or query start columnsas options</div><div class="">- and/or .. some sort of colour code on the row that shows long running queries</div><divclass=""><br class="" /></div><div class="">- and the key request — a context menu item that would allowtermination of the pid via pg_terminate_backend</div><div class=""><br class="" /></div><div class=""><br class="" /></div><divclass="">it would let us have a monitor on activity (the graphs are great) .. and a refresh to see who’s takingthe cpu … and a way to kill the process — all on the dashboard.</div><div class=""><br class="" /></div><div class=""><brclass="" /></div><div class=""><br class="" /></div><div class="">thanks again. and truly, the more I play,the more I appreciate what you have done.</div><br class="" /><div class=""><div class="" style="color: rgb(0, 0, 0);letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal;widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space;-webkit-line-break: after-white-space;"><div class="" style="color: rgb(0, 0, 0); letter-spacing: normal; orphans:auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing:0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><divclass="" style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent:0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><span class="Apple-style-span"style="border-collapse: separate; font-variant-ligatures: normal; font-variant-position: normal;font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; line-height: normal;orphans: 2; text-indent: 0px; widows: 2; border-spacing: 0px;"><div class="" style="color: rgb(0, 0, 0); font-family:Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing:normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows:2; word-spacing: 0px; -webkit-text-stroke-width: 0px; -webkit-text-decorations-in-effect: none;"><b class="" style="font-weight:bold;"><span class="Apple-style-span" style="font-weight: bold;"><span class="Apple-style-span" style="font-weight:bold;"><span class="Apple-style-span" style="font-weight: bold;"><br class="Apple-interchange-newline"/>Doug Easterbrook</span></span></span></b></div><div class="" style="color: rgb(0, 0, 0);font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing:normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows:2; word-spacing: 0px; -webkit-text-stroke-width: 0px; -webkit-text-decorations-in-effect: none;"><span class="Apple-style-span"><bclass="" style="font-weight: bold;"><span class="Apple-style-span" style="font-weight: bold;"><spanclass="Apple-style-span" style="font-weight: bold;"><span class="Apple-style-span" style="font-weight: bold;">ArtsManagement Systems Ltd.</span></span></span></b></span></div><div class="" style="color: rgb(0, 0, 0); font-family:Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing:normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows:2; word-spacing: 0px; -webkit-text-stroke-width: 0px; -webkit-text-decorations-in-effect: none;"><a class="" href="mailto:doug@artsman.com">mailto:doug@artsman.com</a></div><divclass="" style="color: rgb(0, 0, 0); font-family: Helvetica;font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans:2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;-webkit-text-stroke-width: 0px; -webkit-text-decorations-in-effect: none;"><a class="" href="http://www.artsman.com">http://www.artsman.com</a></div><divclass="" style="color: rgb(0, 0, 0); font-family: Helvetica;font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans:2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;-webkit-text-stroke-width: 0px; -webkit-text-decorations-in-effect: none;">Phone (403) 650-1978</div></span></div></div></div></div><brclass="" />
Hi On Thu, Nov 17, 2016 at 3:43 PM, Doug Easterbrook <doug@artsman.com> wrote: > 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. That's already logged at https://redmine.postgresql.org/issues/1812 > 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. https://redmine.postgresql.org/issues/1975 > 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). Personally I prefer it not auto-updating. Makes it easier to read without it changing while you're halfway through. > what is missing are a couple of helpful things: > - the state change and/or query start columns as options Yeah, I think what we need to do is either allow users to select which columns they see in the preferences, or use the subnode control so you can expand a row and see the additional info. Which do you think would be preferable? > - 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:doug@artsman.com > http://www.artsman.com > Phone (403) 650-1978 > -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Re: Pgadmin4: ability to terminate the backend process from the list of processes and highlight activity
От
Doug Easterbrook
Дата:
hi Dave:
Doug Easterbrook
Yeah, I think what we need to do is either allow users to select which
columns they see in the preferences, or use the subnode control so you
can expand a row and see the additional info. Which do you think would
be preferable?
you asked about this — with our own users, we are finding that more and more people have wide monitors … which lends to people having the ability to show lots of columns on any list.
if the columns are resizeable (and perhaps moveable), then I think I’d lean towards customizing columns. That allows more date across the screen. That way you can see more more rows, and therefore more processes.
it it not always that you want extra columns … and preferences as to which — is good.
so my recap:
— column resizing
— all in one row
— customizable columns
in order to see most date at one time.
I hope that helps.
Doug Easterbrook
Arts Management Systems Ltd.
Phone (403) 650-1978
On Nov 18, 2016, at 2:43 AM, Dave Page <dpage@pgadmin.org> wrote:Hi
On Thu, Nov 17, 2016 at 3:43 PM, Doug Easterbrook <doug@artsman.com> wrote: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.
That's already logged at https://redmine.postgresql.org/issues/1812why 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.
https://redmine.postgresql.org/issues/1975in 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).
Personally I prefer it not auto-updating. Makes it easier to read
without it changing while you're halfway through.what is missing are a couple of helpful things:
- the state change and/or query start columns as options
Yeah, I think what we need to do is either allow users to select which
columns they see in the preferences, or use the subnode control so you
can expand a row and see the additional info. Which do you think would
be preferable?- 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:doug@artsman.com
http://www.artsman.com
Phone (403) 650-1978
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support
Вложения
On Fri, Nov 18, 2016 at 2:33 PM, Doug Easterbrook <doug@artsman.com> wrote: > hi Dave: > > Yeah, I think what we need to do is either allow users to select which > columns they see in the preferences, or use the subnode control so you > can expand a row and see the additional info. Which do you think would > be preferable? > > > you asked about this — with our own users, we are finding that more and > more people have wide monitors … which lends to people having the ability > to show lots of columns on any list. > > if the columns are resizeable (and perhaps moveable), then I think I’d lean > towards customizing columns. That allows more date across the screen. > That way you can see more more rows, and therefore more processes. > > it it not always that you want extra columns … and preferences as to which — > is good. > > so my recap: > — column resizing > — all in one row > — customizable columns > > in order to see most date at one time. > > > I hope that helps. Makes sense - https://redmine.postgresql.org/issues/1977 Thanks! -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company