CODEWITHSUNDEEP
windowspgadmin-4
Cardin
Cardin

Reputation: 5507

PgAdmin4 unable to query or view data

I have a very basic PostgreSql table. Despite the simple table schema, I cannot query it via PgAdmin4.

The View Data option is unresponsive; Query Tool option becomes unresponsive after a few attempts in opening and closing the panel. When the Query Tool is eventually (somehow) launched, a trivial SQL statement like

SELECT * FROM test_table

will spin forever and never display.

View of Database

The diagram above shows the exact same table, which is okay under PgAdmin3.

The table was created empty. Then added with a row. But it threw errors about not having a Primary Key. Which also threw errors when I tried to set a Primary Key. So I used TeamPostgreSql to set a Primary Key. So all is good under PgAdmin3 now. Hence I'm really curious about what's going on with PgAdmin4?

Upvotes: 43

Views: 115908

Answers (14)

Stefan Weijers
Stefan Weijers

Reputation: 1

Also had this issue (reproducible multiple browsers and laptops). We figured out that setting PGAdmin k8 pod to be observed by Odigos (eBPF tracing) somehow caused this issue.

Upvotes: 0

Ecem
Ecem

Reputation: 1

I had the similar problem by combining two of the above solutions it worked for me:

  1. I changed Hostname from localhost to IP address 127.0.0.1
  2. Click file on menu bar >> click reset layout

Upvotes: 0

Edward
Edward

Reputation: 55

Personally, I had a dumb issue. I had my DATABASE_URL pointing to another server

DATABASE_URL='postgres://postgres:root@localhost:5432/wrong-database'.

Even though my DATABASE_NAME='correct-database'.

And in my settings.py I was running

db_from_env = dj_database_url.config(conn_max_age=600) DATABASES['default'].update(db_from_env).

Please make sure your .env file is correct.

Upvotes: 0

Orion Cygnus
Orion Cygnus

Reputation: 198

Faced a similar issue where the problem was caused by Firefox, pgADmin 4. Launching pgAdmin in Chrome solved the issue.

Upvotes: 1

shane
shane

Reputation: 171

I had a similar problem.

For me the Query Tool did render, however I could not see the Query Tool until after I expanded the view.

Then even after expanding I was not able to see the result of the query until I ran ( File -> Reset Layout ) as Guillaume Raymond suggest.

Before Expand

After Expand

After Running Reset Layout

Upvotes: 6

trungkien_hust
trungkien_hust

Reputation: 21

You can remove pgadmin4, then reinstall it. It worked for me. I used Ubuntu 18.04. Here is my command on terminal:

  1. sudo apt autoremove pgadmin4
  2. sudo apt install pgadmin4 pgadmin4-apache2 -y

Upvotes: 0

Erich13
Erich13

Reputation: 69

I had the same problem (version 4.18). Only the following worked for me:

  1. Create a new server group (!) by right-clicking on "servers" in the left-hand navigation.

  2. In this new group I created the desired connection to the database (with host name 127.0.0.1)

After that I could finally work with it

Upvotes: 0

AKumar
AKumar

Reputation: 19

This problem I experienced with the internet explorer browser where the query tool was not loading at all. It just kept on spinning with a circle. I solved this issue by using chrome browser.

When you launch pgadmin4 it launches in internet explorer by deafult. it has a key attached to it like

http://127.0.0.1:57756/?key=0371aabd-b4c7-4454-8234-b1234416d7e5e.

you can just paste the above url in the browser directly and the pgadmin4 will open and query tool works in it. Or you cna use cmd and paste the belwo command and pgadmin4 will open as a standlone application rather tahn another tab in the browser and you cna use it like old pgadmin3.

C:\windows\system32>"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --app=http://127.0.0.1:57756/?key=0371aabd-b4c7-4454-8234-b1234416d7e5e

Upvotes: 0

CamW
CamW

Reputation: 3363

I fixed this by opening the connection, changing just the connection name and saving the connection.

Based on other comments, I'd say there is likely some difference in the persisted format of the connection and they need to be resaved by the new version to work.

Upvotes: 2

dbabackup
dbabackup

Reputation: 11

Warning: You may need to recreate connections.

This worked for me.

1.) Shutdown pgadmin4 3.1

2.) Delete folder: C:\Users\YOUR_USERNAME\AppData\Roaming\pgAdmin

Upvotes: 1

Fernando Fabreti
Fernando Fabreti

Reputation: 4366

I'm running pgAdmin4 v3.0 and I've put localhost as host name.

I mean, left panel > servers > create > server and then connection tab > host name

I could not query tables, clicking on view/edit data > all rows had no results (nor error log entries).

After I changed server name from localhost to 127.0.0.1, all worked as expected!

I hope it helps, because I've lost so much time on this and could not find a proper answer.

Upvotes: 65

Guillaume Raymond
Guillaume Raymond

Reputation: 1824

I find a way to view query result on Data Output window using the "Reset Layout" command from File menu. Save your current work (query) before as it will kind of restart pgAdmin4. Tested with pgAdmin 2.1

File -> Reset Layout

Upvotes: 67

Alexeey
Alexeey

Reputation: 41

Try naming your columns with lower case letters.

Or try with a blank query and write the SQL commands manually:

SELECT * FROM “test_table”
ORDER BY “Apple” ASC

I think this is a bug. The command the pgAdmin 4 is sending, does not contain the double quotes in the order command on the column name, and if you have upper case letters, SQL is going to convert them to lower case letters, thus not finding the sorting criteria.

Upvotes: 4

Murtuza Z
Murtuza Z

Reputation: 6017

1) First delete the log file to get rid of older logs

2) Start pgAdmin4.

3) Try to view data again

Can you check log file for any errors & paste it here?

Linux log location: ~/.pgadmin/pgadmin4.log

Windows log location: C:\Users\YOUR_USERNAME\AppData\Roaming\pgAdmin\pgadmin4.log

Upvotes: 4

Related Questions