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

Поиск
Список
Период
Сортировка
От Dave Page
Тема Re: Pgadmin4: ability to terminate the backend process from the list of processes and highlight activity
Дата
Msg-id CA+OCxoxsZBGjFj5riSDpCC4krg5+vn+_dTmwiqMP6f-1ThTtDA@mail.gmail.com
обсуждение исходный текст
Ответ на Pgadmin4: ability to terminate the backend process from the list of processes and highlight activity  (Doug Easterbrook <doug@artsman.com>)
Ответы Re: Pgadmin4: ability to terminate the backend process from the list of processes and highlight activity
Список pgadmin-support
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



В списке pgadmin-support по дате отправления:

Предыдущее
От: Dave Page
Дата:
Сообщение: Re: UI Odditiies in the Query Tool
Следующее
От: rvt
Дата:
Сообщение: My issue with pgAdmin 4