RE: pgAdmin v4.1 - positive feedback

[l...@laurent-hasson.com]

Let me join the chorus... To some degree, my complaints seem minor today 
compared to 1y ago, so it’s much improved. My organization made the move to 
Postgres 11, so I had no choice but to get re-acquainted with PGAdmin4 since 
III doesn't work at all anymore.

So here are some suggestions. I know, it's easy to make suggestions, and I wish 
I knew how to code the client-side so I could make some contribs, but I also 
think those suggestions may be fairly simple. Could you suggest some 
participation I could provide to help? Ticket, tracking, maybe doc?

  - One of the simplest features of PGAdmin III that I find myself missing 
EVERY DAY is simply the timer on the bottom right of the query window. When 
running queries, I often know how long they will take and so having that simple 
timer while the query runs is very useful 😊

  - Another simple feature is the ability to continue editing some queries 
while one query runs. I often manage multiple queries and on III, i would run 
one query while editing/fixing/preparing the next query in the same editor. I 
know I could open another editor but it's just not as convenient, and on the 
browser, no quick ALT-TAB.

  - More importantly, I find the backend still flaky. I am still experiencing 
frequent backend errors, or reaching a state where the whole front-end is 
broken. Short of going to the system tray and killing the backend server, there 
is no other way. I used to go to the Task Manager until I recently discover the 
"kill server" option on the tray. It'd be nice to have a menu option to 
"restart" the server from the browser UI and allow the UI to just survive a 
backend meltdown.

Thank you,
Laurent.

> -Original Message-
> From: Mark Murawski 
> Sent: Monday, January 21, 2019 11:33
> Cc: pgadmin-support@lists.postgresql.org
> Subject: Re: pgAdmin v4.1 - positive feedback
> 
> Hi All,
> 
> As a hard core pgadmin3 user I was also really bummed when I first started
> trying to use pgadmin4.
> 
> I also also pretty happy with the progress so far, but there's still some 
> oddities
> and missing features that keeps me on pgadmin3... so much that I actually
> started my own local branch of pgadmin3-lts and started making improvements
> to make it more postgres-10 friendly since it's an app I love so much.
> 
> The biggest issue is the core infrastructure of pgadmin3 is really unfriendly 
> to
> newer libraries, so I'm stuck running this on an older vm just so I can build 
> the
> thing!
> 
> But... pgadmin4 is marching along and I am looking forward to when I can use
> it as my full-time DB interface.
> 
> Thanks to all the developers for keeping on.
> 
> 
> On 1/20/19 2:54 PM, Jack Royal-Gordon wrote:
> > Thanks for your post, Richard. Like you, I looked at pgAdmin 4 a
> > couple years ago. I decided then that it wasn’t ready for me, so I
> > went back to pgAdmin III. Your post convinced me to go back and take
> > another look. I only just loaded it, but my immediate impression is far more
> positive.
> > I’m not one of those who trashed the developers for the choices they
> > made, I know that building something like this takes time and will
> > involvd some unfortunate decisions that are nevertheless difficult to
> > backtrack on. I’m happy to see that the project has moved forward to
> > where it is at now. I will be evaluating it in the coming days and
> > weeks hopefully.
> >
> > Thanks,
> >
> > Jack
> >
> >> On Jan 20, 2019, at 10:31 AM, Richard Brockie
> >> mailto:richard.broc...@gmail.com>> wrote:
> >>
> >> Hi,
> >>
> >> I've subscribed to this list specifically to give this positive feedback!
> >>
> >> Like many others, I shared the initial disappointment with the early
> >> pgAdmin 4 releases. Things improved greatly when pgAdmin 4 started
> >> using the default system browser, and now moving to v4.1 from v3.6
> >> yesterday, I'm very pleased to say that I find I am enjoying using
> >> pgAdmin again!
> >>
> >> Thanks & best wishes,
> >> --
> >>     R.
> >>
> >> Richard Brockie
> >>
> >> Real-time bicycle race management - www.ontheday.net
> >> 
> >
> 
> 

RE: pgAdmin v4.1 - positive feedback

[l...@laurent-hasson.com]

Comments inlined.

Thank you,
Laurent.

From: Dave Page 
Sent: Tuesday, January 22, 2019 04:42
To: l...@laurent-hasson.com
Cc: Mark Murawski ; 
pgadmin-support@lists.postgresql.org
Subject: Re: pgAdmin v4.1 - positive feedback

Hi

On Tue, Jan 22, 2019 at 3:55 AM 
l...@laurent-hasson.com<mailto:l...@laurent-hasson.com> 
mailto:l...@laurent-hasson.com>> wrote:
Let me join the chorus... To some degree, my complaints seem minor today 
compared to 1y ago, so it’s much improved. My organization made the move to 
Postgres 11, so I had no choice but to get re-acquainted with PGAdmin4 since 
III doesn't work at all anymore.

So here are some suggestions. I know, it's easy to make suggestions, and I wish 
I knew how to code the client-side so I could make some contribs, but I also 
think those suggestions may be fairly simple. Could you suggest some 
participation I could provide to help? Ticket, tracking, maybe doc?

  - One of the simplest features of PGAdmin III that I find myself missing 
EVERY DAY is simply the timer on the bottom right of the query window. When 
running queries, I often know how long they will take and so having that simple 
timer while the query runs is very useful 😊

Would having a timer display on the "Waiting for query to execute..." busy 
screen work? You'd then see that whilst it was executing, followed by the 
"Execution complete" notification (which includes the time), and of course the 
time that's shown on the history panel.
[Laurent Hasson] Yes, that would work.


  - Another simple feature is the ability to continue editing some queries 
while one query runs. I often manage multiple queries and on III, i would run 
one query while editing/fixing/preparing the next query in the same editor. I 
know I could open another editor but it's just not as convenient, and on the 
browser, no quick ALT-TAB.

Please log a feature request at 
https://redmine.postgresql.org/projects/pgadmin4/issues/new. Restricting the 
busy screen to the 4 output tabs doesn't seem like it would be too hard. My 
main concern would be the UX of doing so.
[Laurent Hasson] Understood on the UX and I can see why it was done that way. I 
guess I am used to the behavior of III where that is possible: greater brain 
bandwidth imho than having to switch tabs. Running a large query is something I 
do often and I kinda work in parallel all the time. You can do that in Toad, 
SQLServer Studio, or PGAdmin III so I think it’s a behavior most devs would be 
familiar with… Feature #3920 has been created.

You can switch between top level tabs with Alt/Option + Shift + [ and 
Alt/Option + Shift + ] by default. That can be changed under File -> 
Preferences -> Browser -> Keyboard Shortcuts.
[Laurent Hasson] Ah, so this is interesting. I have been having problems with 
keyboard shortcuts. Even saving has been problematic without clicking on the 
save icon. I guess I can’t figure out what the keyboard config is. I have an 
older IBM mechanical keyboard, on Windows, what’s the combination of keys by 
default (I haven’t customized that)?. But anyways, I have found getting rid of 
the brain scarification around Alt-Tab really hard… 😊


  - More importantly, I find the backend still flaky. I am still experiencing 
frequent backend errors, or reaching a state where the whole front-end is 
broken. Short of going to the system tray and killing the backend server, there 
is no other way. I used to go to the Task Manager until I recently discover the 
"kill server" option on the tray. It'd be nice to have a menu option to 
"restart" the server from the browser UI and allow the UI to just survive a 
backend meltdown.

In what way is it flaky? It's been designed so that even when errors occur, 
they typically only affect that operation (unlike pgAdmin 3 which would just 
crash entirely). The whole architecture makes it inherently far more robust 
against such issues. Please log tickets and provide logs showing any errors, 
particularly un-recoverable ones.
[Laurent Hasson] I’ll have to capture logs or screenshots yes… Now that I know 
how to file issues, I’ll follow up with more details. But I get a variety of 
system errors on a regular basis and the UI is no longer responsive: I can 
click on a schema node for example and there would be the “progress” twirling 
icon going on forever, and the main dashboard would show red tiles with error 
messages, and I wouldn’t be able to launch a new query window or anything. 
Short of closing the browser window, killing the server and restarting, I 
haven’t found a way to recover.

Thank you,

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Long running queries time out

[l...@laurent-hasson.com]

Hello,


I recently migrated from Postgres 9.6 to 11 and with that moved from PGAdmin 
III to V4. I am experiencing an issue that i never experienced before.


I run a lot of queries against large databases which can take 3-4h to run. When 
i use PGAdmin 4, those queries time out. i.e., i get an error that the 
connection was lost and no results are returned. Some of those queries to 
updates and i can confirm afterwards that the query did complete and i cannot 
see in the backend anything suspect in the logs.


When i log into the backend and run queries via psql, all is good. So something 
between the server and PGAdmin is causing connections to time out, even thought 
the queries seem to complete properly.


Any insight as to how this may be happening, any setting i should check etc...? 
I have never experienced this before on 9.6/III so i am a bit at a loss.


Thank you,

Laurent.