Re: Pgadmin4: ability to terminate the backend process from the list of processes and highlight activity

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.

Doug Easterbrook
Arts Management Systems Ltd.
mailto:doug(at)artsman(dot)com
http://www.artsman.com
Phone (403) 650-1978

> On Nov 18, 2016, at 2:43 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>
> Hi
>
> On Thu, Nov 17, 2016 at 3:43 PM, Doug Easterbrook <doug(at)artsman(dot)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(at)artsman(dot)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(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgadmin-support