Re: [pgadmin-support] Pgadmin4: ability to terminate the backend process from the list of processes and highlight activity
Hi On Thu, Nov 17, 2016 at 3:43 PM, Doug Easterbrook 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:d...@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
[pgadmin-support] My issue with pgAdmin 4
Hey All, first of all... I love open source, and I hate to give negative feedback and it took me a while to decide to to give the feedback or just keep it to myself... I tried pgAdmin4 a few times now, but I cannot get used to it, here are my biggest issues with it. 1) The windows animations slow thing's down to much. Please have a option to turn all animations off. 2) It's a single window application and it doesn't allow me to drag windows around on my desktop, hide the windows I don't need etc. 3) Some icons or fonts look very blurred on my screen (5K screen 27" imac).. 4) The menu is not where where it suppose to be. 5) Some screens appear slow to me with a 'loading' icon, even without the windows it takes took long to 'draw' the screen. Where in pgAdmin 3 a lot of items are near instance, in pgAdmin4 it takes time to display. 6) pgAdmin3 Memory : 60Mb (4 threads), pgAdmin4 Memory : 330Mb (15 threads) 7) Clicking on a table in the tree doesnt do anything in pgAdmin4, in pgAdmin3 it shows me the table definition. For me, the fact that's a single window application is the biggest issue of pgAdmin4, it just feel very right and natural, second issue is the slowdowns, it doesn't feel 'snappy', every action takes time and/or doesn't act like a desktop application. I very much appreciate the work that has been into the application and I really hope I am the only one with the above items. cheers, -- View this message in context: http://postgresql.nabble.com/My-issue-with-pgAdmin-4-tp5930941.html Sent from the PostgreSQL - pgadmin support mailing list archive at Nabble.com. -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
Re: [pgadmin-support] 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:d...@artsman.com http://www.artsman.com Phone (403) 650-1978 > On Nov 18, 2016, at 2:43 AM, Dave Page wrote: > > Hi > > On Thu, Nov 17, 2016 at 3:43 PM, Doug Easterbrook 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:d...@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 signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [pgadmin-support] Pgadmin4: ability to terminate the backend process from the list of processes and highlight activity
On Fri, Nov 18, 2016 at 2:33 PM, Doug Easterbrook 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 -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
[pgadmin-support] Sortable statistics columns not sorted according to type
Hello, sortable columns like "tuples inserted" should be sorted according to their type (=integer) not as string. Regards Andreas -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
Re: [pgadmin-support] Sortable statistics columns not sorted according to type
On Fri, Nov 18, 2016 at 2:18 PM, Andreas Kinzler wrote: > Hello, > > sortable columns like "tuples inserted" should be sorted according to their > type (=integer) not as string. Thanks, this has already been logged: https://redmine.postgresql.org/issues/1938 -- 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
