Thread: pgadmin3 incredibly slow over network

If I use pgAdmin3 to query a remote database with SELECT * FROM big_table, the whole thing takes 1.5 minutes until I get my results.

If I run the same query, from the same computer, to the same remote database, using a different client (HeidiSQL, or even pgsql), it takes 5 seconds.

I run pgAdmin 1.22.2 on Windows 10, and the postgreSQL database is on Linux. The postgreSQL version is 9.3, but it doesn't seem to be specific to the

version. The same happens on 9.4. The large performance differences happen in other queries as well, to various degrees of difference.

What could be causing this?

Hi Ricardo,

I tried to reverse the order (first HeidiSQL then pgAdmin), but the result was the same.

The following is for EXPLAIN SELECT * FROM quotations

HeidiSQL:

QUERY PLAN

Seq Scan on quotations  (cost=0.00..5177.66 rows=80566 width=629)

PostgreSQL:

QUERY PLAN

Seq Scan on quotations  (cost=0.00..5177.66 rows=80566 width=629)

If I do EXPLAIN ANALYZE SELECT * FROM quotations I get:

HeidiSQL:

Seq Scan on quotations  (cost=0.00..5177.66 rows=80566 width=629) (actual time=0.007..93.069 rows=80570 loops=1)

Total runtime: 180.094 ms

PostgreSQL:

Seq Scan on quotations  (cost=0.00..5177.66 rows=80566 width=629) (actual time=0.024..133.131 rows=80570 loops=1)

Total runtime: 234.574 ms

By the way HeidiSQL reports the following about SELECT * FROM quotations:

Affected rows: 0  Found rows: 80,570  Warnings: 0  Duration for 1 query: 0.000 sec. (+ 4.125 sec. network)

Given that the analyze query on pgAdmin shows similar numbers to those via HeidiSQL, it looks like the vast majority of the delay might be network transfer.

What could pgAdmin be doing that slows down network I/O so significantly?

Hi Nikita,

Your message helped me to discover HeidiSql which is (for my needs), even though its implementation for Postgres is experimental, much more convenient as pgAdmin v4.x

It is not as “friendly” as pgAdmin III but is intuitive enough to accomplish basic tasks.

Let’s hope that HeidiSql will remain a simple application and that they will not try to change its interface to browser.

I was blocked with PostgreSql 9.6 because of pgAdmin compatibility.

Now, with HeidiSql, I can consider to upgrade.

@ Akshay Joshi

Sorry about it.

Your strategical decision to rewrite pgAdmin for browser was a mistake.

Every new release corrects probably some bugs but it remains hardly usable.

I do try every new release and have to fall back on pgAdmin III.

I follow the discussions and read about problems encountered by other pgAdmin users. It is not encouraging at all.

I have reported a couple of bugs, mainly due to browser integration, which have not been fixed and probably never will.

Regards

If I use pgAdmin3 to query a remote database with SELECT * FROM big_table, the whole thing takes 1.5 minutes until I get my results.

If I run the same query, from the same computer, to the same remote database, using a different client (HeidiSQL, or even pgsql), it takes 5 seconds.

I run pgAdmin 1.22.2 on Windows 10, and the postgreSQL database is on Linux. The postgreSQL version is 9.3, but it doesn't seem to be specific to the

version. The same happens on 9.4. The large performance differences happen in other queries as well, to various degrees of difference.

What could be causing this?