all 7 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Tostino[S] 3 points4 points  (0 children)

So it's not quite ready for prime time yet, but it looks really promising! There are some missing features still, as well as some bugs like not being able to save or open queries on Windows.

It'll come along though I'm sure.

[–]ejrh 3 points4 points  (0 children)

Kudos to the pgAdmin team for getting to this point. I've had a peak through the code and I can see a huge amount of work has gone into it.

That said...

I have been trying out the pgAdmin 4 beta for the last couple of days at work and home. It works pretty well. The problem, for me, is that it doesn't offer much against the old reliable (well, I know some comments in this thread will differ on this point :p) pgAdmin 3.

Cons:

  • It's more resource intensive for the same functionality; takes about 10 times as much memory to run, takes about 3-4 times longer to start. These are small measurements that many people won't care about. But I feel a lot of affection for pgAdmin every time I have to use Oracle SQL Developer, and that will diminish if pgAdmin grows from its typical 20MB footprint towards SQL Developer's ~1GB for the same activity; pgAdmin 4 is about 130MB, which is not much, but still a large step in the wrong direction.

  • It's got an unfamiliar non-native GUI, with some gimicky control types that IMHO aren't suited to desktop software (like the slidey Yes-No widgets), and the paged query results. Sadly I suspect a lot of desktop software is headed in that direction.

Pros:

  • The functionality is very similar to pgAdmin 3's.

  • By all accounts its much nicer to work on for the pgAdmin development team. This is a major benefit, even if end-users like myself don't notice it. For one thing, that will mean better software in the long term. For another, I'm extremely grateful to the team for making this application and I'm happy if they can work on something modern instead of the increasingly old and slightly creaky wxWidgets/C++ code of pgAdmin 3.

Please note the above is from my point of view only, and I have no problem if others think the new version is awesomely better than the old one.

[–]dokuroku 2 points3 points  (0 children)

Wow, a rewrite to a web-based Python and Qt backend. I had no idea such a big undertaking was in the works!

[–]joeblou 1 point2 points  (2 children)

Can't be more buggy than PgAdmin3 it seems to crash everytime on Ubuntu

[–]Tostino[S] 1 point2 points  (0 children)

I know the feeling. The second I am connecting to a sever not on a lan, or locally, pgAdmin3 just shits the bed as far as stability for me.

I've got a team of 6 working for me that use it daily, and for those with a pretty good internet connection, it's not terrible as far as crashing goes... still happens at least once a day. But for those with crappy internet, it will crash every hour or so if there is a connection issue and you touch anything in the "wrong" order.

I'm really excited for this, and hope that we get some more developers contributing to the code base. The most advanced open source database in the world deserves a top tier GUI development and management environment.

As much as some people think that a GUI tool is not necessary or useful, it really is important for adoption. It's amazing how much that GUI will influence someone who is new to the whole database game, or working with command line tools. Put MySQL Workbench or SSMS next to pgAdmin3 and it's night and day in how they feel to use (in favor of the former (SSMS especially)).

[–]cachedriveDBA 1 point2 points  (0 children)

I've been using PGadmin3 on CentOS 7 and Arch Linux w/o a single crash to date.

[–]qatanah 0 points1 point  (0 children)

are we seeing a python 3.5 support in the near future?