I've installed Postgresql 11 and pgAdmin4 (version 4.5) and while I'm able to create tables in a new database, if I attempt to SELECT or INSERT into those tables I always get a message 'Not connected to the server or the connection to the server has been closed.' in the "Messages" tab in pgAdmin 4. If, however, I open the SQL Shell I can execute a SELECT on a table that I've attempted to insert into from pgAdmin and it shows that the rows have been inserted.

**Problem:** I've installed the latest web version of pgAdmin4: 9.6, using the official pgAdmin Docker image: dpage/pgadmin4, and all seems to be working fine, except the main tool: "query tool", when I click on "query tool" icon, it just keeps opening blank tabs. (can't even close them) **Tried:** - logging off - restarting image - resetting layout - reinstalling 9.6 - trying with 9.5 - trying with 9.1 **Notes:** - I've tested the DB and connection string of the same DB on my Desktop version of pgAdmin(also 9.6) and everything works, including "query tool" (so the DB and connection string are fine...have only issues with this docker web versions)

In PgAdmin III, it is possible to change the font and colors for the query tool editor window in the options menu: I can't find any similar settings in the preferences window for PgAdmin 4. How and where can I change the font and colors?

I was sitting on pg14 for some time, while the postgresql package updates accumulated all the way up to 17, so the result of pg_lsclusters looks like this:

Ver Cluster Port Status Owner    Data directory              Log file
14  main    5432 online postgres /var/lib/postgresql/14/main /var/log/postgresql/postgresql-14-main.log
15  main    5433 online postgres /var/lib/postgresql/15/main /var/log/postgresql/postgresql-15-main.log
16  main    5434 online postgres /var/lib/postgresql/16/main /var/log/postgresql/postgresql-16-main.log
17  main    5435 online postgres /var/lib/postgresql/17/main /var/log/postgresql/postgresql-17-main.log

I only have a connection to version 14 in my pgAdmin panel, but how do I add connections for other servers? They require the password for postgres which I either don't know or don't remember.
The thing tripping me up is I think I had a setup step a while ago where I created a copy of postgres user with the same name as the admin account in the OS, or the package created it for me on install. Thus I've used that admin role in place of postgres for superuser needs and forgot about original superuser. Possibly I've set a password for postgres (most likely generated one) within old version of pgAdmin, saved it and completely forgot about it afterwards.
But now I need to actually migrate my database to the newest version and thus the problem at hand. Versions: - postgreSQL - 17.4 - pgAdmin - 9.1 - Ubuntu - 22.04.5 LTS **EDIT**: I can "enter" into the other cluster with sudo --user=postgres psql --port=5435 (without a password), but not when calling it with TCP/IP socket sudo --user=postgres psql --host=localhost --port=5435. However sudo --user=postgres psql --host=localhost, which enters into 5432 server, does ask for password, which matches password of the OS admin account.
This does confirm that I in fact changed the password for postgres db user of 5432 server in order to create a connection in pgAdmin, and other clusters were created by the package updates according to their mystical rules.
It still begs the question what IS the proper way of handling default postgres user for pgadmin connection while also preserving linux way of handling it as an OS user? Because now I think setting a password for it to connect was not a right call.

We use the pgAdmin4 version 3.1 on Red Hat connecting to a server PostgresQL 9.6. In the log of the server, I notice some errors generated by the pga4dash : ERROR: column "waiting" does not exist at character 193 Indeed, the column waiting has been renamed to wait_event in Postgresql 9.6. I tried to upgrade the pgadmin4 package by using : yum updgrade pgadmin4 The upgrade was realized without problem but it's still running the oldest version 3.1 instead of the new downloaded (after a reload of httpd daemon) How can I do to use the newest pgadmin4 version downloaded? I search on the documentation of pgadmin and there are no notes about an upgrade of the pgAdmin4

Let's say I have 4 SSH tunnels to different remote servers, each having different PostgreSQL databases up and running. Each tunnel is mapped to a specific port on my local machine (localhost) as follows:

ssh -f -N -L 1234:127.0.0.1:5432 userA@serverA
ssh -f -N -L 1235:127.0.0.1:5432 userB@serverB
ssh -f -N -L 1236:127.0.0.1:5432 userC@serverC
ssh -f -N -L 1237:127.0.0.1:5432 userD@serverD

Now, in my PostgreSQL .pgpass file I can refer for example to my databases with:

# hostname:port:database:username:password
127.0.0.1:1234:database_a:pg_user_a:postgres_password_a
127.0.0.1:1235:database_b:pg_user_b:postgres_password_b
127.0.0.1:1236:database_c:pg_user_c:postgres_password_c
127.0.0.1:1237:database_d:pg_user_d:postgres_password_d

And this is fine. But now, within the pgAdmin4 docker image (https://hub.docker.com/r/dpage/pgadmin4/) the port mapping on the docker 'localhost' cannot be chosen by the user; it's randomly getting assigned a value. Therefore, and because I cannot guess in advance all the ports that will be used for the tunneling, I must change the .pgpass file using wildcards in this way:

127.0.0.1:*:database_a:pg_user_a:postgres_password_a
127.0.0.1:*:database_b:pg_user_b:postgres_password_b
127.0.0.1:*:database_c:pg_user_c:postgres_password_c
127.0.0.1:*:database_d:pg_user_d:postgres_password_d

This is always fine. I guess. (unless I know which IP range is used by pgAdmin4 internally and if I can set up this exact same range in the pgpass file but I don't think this is possible.) Now, what if I'd like to connect to the default postgres maintenance database with the default postgres user on each?

127.0.0.1:*:postgres:postgres:postgres_password_a
127.0.0.1:*:postgres:postgres:postgres_password_b
127.0.0.1:*:postgres:postgres:postgres_password_c
127.0.0.1:*:postgres:postgres:postgres_password_d

How could I let pgAdmin4 knows which password to use with which server as all first four fields are now exactly the same? Setting the same password on all servers, reducing the pgpass file to this single line:

127.0.0.1:*:postgres:postgres:unique_postgres_password

is definitely not an option as I cannot change those {databasenames:usernames:passwords} myself. The local ports being randomly assigned, I guess I'll have to play with the local IP but I'm not successful for the moment as it seems to be automatically set to 127.0.0.1. This latter case is the most extreme one, but one can easily imagine the same issue with two different databases; a pre-production and a production one, having both the same {database:username} but different passwords. Doc: https://www.postgresql.org/docs/14/libpq-pgpass.html

(pgadmin4:10053): Gtk-WARNING **: Theme parsing error: gtk.css:8645:2: Junk at end of value for padding-left (pgadmin4:10053): Gtk-WARNING **: Theme parsing error: gtk.css:13132:11: 'shadowbox' is not a valid property name Can someone please help figure out why? Also help me with a solution.

I want to use GUI, e.g., PgAdmin 4, on a PotsgreSQL on Red Hat Enterprise Linux 9, and my Linux username has SUDO permissions. With command line, I will login through SSH, and call sudo su - postgres, then call psql as the PostgreSQL superuser to connect through the UNIX socket at /run/postgresql/.s.PGSQL.5432. However, if using PgAdmin 4, its connection has a tab of "SSH Tunnel", but I am not sure whether I can add sudo su - postgres and connect through the UNIX socket. Another workaround is to add a password to the superuser postgres, then connect through SSH tunnel to the port 5432 on the localhost. But, the additional step of setting password is not very elegant. We have seen a similar question [PgAdmin 4 - How to connect to database using unix socket via ssh tunnel?](https://dba.stackexchange.com/questions/279060/pgadmin-4-how-to-connect-to-database-using-unix-socket-via-ssh-tunnel) . However, I want to access the UNIX socket as postgres while this user does not have SSH. So, I have a SUDO Linux login and hope to access the UNIX socket as postgres, like doing sudo su - postgres in CLI. For this specific part, I could not find the answer in the referred article above. Thank you for your understanding. We highly appreciate any hints and suggestions.

Even though it might sound related to this question , it isn't, because I'm intreseted in the use of unix sockets instead of TCP/IP ones. However, I am unable to connect to a remote PostgreSQL database using unix sockets and an ssh tunnel with pgAdmin4. pgAdmin always claims a refused connection by the server and asks for a password, which makes me wonder. When sshing into the server and using psql a connection can be made just flawlessly using the unix socket (/var/run/postgresql). Is there anything special that needs to be set to allow such a setup, or might this even be a bug in pgAdmin itself? I'd appreciate any ideas to solve this problem without having to resort on TCP/IP connections on the remote side. I also post some screens from my current config:

I have a production database with 60K database schemas. PgAdmin4 is unusable, I cannot even open "Query Tool" window. I suppose that PgAdmin tries to load database metadata, so that's the reason why it's so slow. Is that true and can it be disabled? Can I do anything to speed it up? I tried to use other DB clients like DBeaver or TablePlus and I have the same problem.

I'm quite experienced with MSSQL and MySQL/MariaDB, but I'm a newbie re PostgreSQL. I got everything to work, except for the odd detail that the admin user which I set up during installation can't "view/edit" tables. The error displayed is: > domain.com refused to connect ### Here's what works I installed PostgreSQL 12.3 and pgAdmin4 both on a Ubuntu 20.04 LTS server (Azure VM, CLI only, no GUI). Everything works, I can log in from a browser (domain.com/pgadmin4), and create databases and tables. ### This doesn't seem to work However, when I right-click on a table (View/edit data -> first 100 rows), then I get the error message: > domain.com refused to connect. ### Equally strange observation Also, on another machine, I use Pentaho Data Integration for ETL purposes. From there, I can connect, create tables (via the automatic SQL code it generates), and I can both write and read tables, not a problem at all. ## Problem My only issue is that the admin user in pgAdmin4 cannot read tables (despite the "Administrator" role). I also turned off ufw (the Ubuntu Firewall), and any IP restrictions in the Azure account (which is effectively a second firewall). I also checked the logfile postgresql-12-main.log, but I didn't see any related entries. I'd really appreciate if someone could give me an idea how to troubleshoot that.

How to backup all functions in pgadmin 4 version 1.6? After executing the below query the backup functions stored in which place? And how to find it? How to know all information is backed up with what's being done? SELECT pg_get_functiondef(f.oid) || E';\n' FROM pg_proc f JOIN pg_namespace n ON f.pronamespace = n.oid WHERE n.nspname = 'schemaname';

I have a frontend written in MS Access that connects to a Postgres backend through ODBC. Sometimes the number of sessions reaches 100 and at that point I get an "ODBC call failed" error. I use PG Admin version 6.13 to administer the database. I noticed under Database activity -> sessions the following after some heavy usage on the database: There are over 70 of these in the session tab, which causes the application to crash. If I close the application, the entries also disappear. Running the SQL returns nothing, as there is no data type with the name "lo" in the table pg_type. The table pg_type is a system table, not one that I created. Any ideas how to fix this excessive number of session entries? And what is this "lo" type?

I installed the latest pgAdmin 4 (v2.1) but I found out that (related thread ), for the moment, the only way to establish a connection through an SSH tunneling is using another outside process, an example in the pgAdmin's forum says: > I setup a tunnel as follows: > > ssh -f dpage(at)hostname(dot)enterprisedb(dot)com -L 5999: hostname.enterprisedb.com:5432 -N > > (...) I was running on Mac, but the same procedure should work on Linux. On Windows, there's a tunnelling app in Putty iirc, but I don't know how to use it offhand. I have found a simple PuTTY tutorial to establish a connection using an SSH Tunnel . The connection is established but it seems, when I try to connect through pgAdmin it fails or is refused (using _127.0.0.1:3306_ or _127.0.0.1:5432_ as the tunnel's destination). Why?

*I already found the solution, I just want to share it in case someone has the same problem.* ### Situation ### Install pgAdmin4 version 4.30 on Linux Mint 20 (Ulyana) and Linux Mint 20.1 (Ulyssa) inside virtualenv. The bulk of pgAdmin4 is a Python web application written using the Flask framework. Therefore, it is an ideal candidate to be implemented in a Python virtualenv as indicated in: [How to Install PostgreSQL with pgAdmin4 on Linux Mint 20](https://www.tecmint.com/install-postgresql-with-pgadmin4-on-linux-mint/) And, [Installing pgAdmin 4 on Linux Mint 20 (ulyana)](https://medium.com/@ogunyemijeremiah/installing-pgadmin-4-on-linux-mint-20-ulyana-741b941479c9) And in Spanish, [Cómo instalar PostgreSQL con pgAdmin4 en Linux Mint 20](https://es.linux-console.net/?p=2457) ### Error ### After finishing the process, when trying to run pgAdmin4 for the **first time**, the following error appears:

Traceback (most recent call last):
  File "venv/lib/python3.8/site-packages/pgadmin4/pgAdmin4.py", line 87, in 
    exec(open(file_quote(setup_py), 'r').read())
  File "", line 449, in 
  File "", line 372, in setup_db
  
  [...]

  File "/home/mint/pgAdmin4/venv/lib/python3.8/site-packages/flask_sqlalchemy/__init__.py", line 575, in get_options
    self._sa.apply_driver_hacks(self._app, sa_url, options)
  File "/home/mint/pgAdmin4/venv/lib/python3.8/site-packages/flask_sqlalchemy/__init__.py", line 908, in apply_driver_hacks
    sa_url.database = os.path.join(app.root_path, sa_url.database)
AttributeError: can't set attribute

In the **second attempt** to execute pgAdmin4 the error shown is:

Traceback (most recent call last):
  File "/home/mint/pgAdmin4/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1705, in _execute_context
    self.dialect.do_execute(
  File "/home/mint/pgAdmin4/venv/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 681, in do_execute
    cursor.execute(statement, parameters)
sqlite3.OperationalError: table version already exists

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "venv/lib/python3.8/site-packages/pgadmin4/pgAdmin4.py", line 94, in 
    app = create_app()
  
  [...]

  File "/home/mint/pgAdmin4/venv/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 681, in do_execute
    cursor.execute(statement, parameters)
sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) table version already exists
[SQL: 
CREATE TABLE version (
	name VARCHAR(32) NOT NULL, 
	value INTEGER NOT NULL, 
	PRIMARY KEY (name)
)

]
(Background on this error at: http://sqlalche.me/e/14/e3q8) 

This situation started to occur in March 2021 and as far as I know, it is identical on both Linux Mint 20 and Linux Mint 20.1. > Note: a more suitable location to put the virtualenv would have been /opt, but for multiple tests I opted for /home from a live USB with Linux Mint 20. Then apply the final changes to my Linux Mint 20.1

I'm new to PostgreSQL.I'm using postgreSQL locally. I used it last time without any issues. Now, when I try login with my login credentials it shows the account is locked message all the time.

I'm working with postgresql on my local machine with Windows 10, in pgadmin4 I can create new Server Groups and new Servers, if I create 2 new server groups and select localhost for the host, I get all the databases I've created on my computer. Is there any way to split all the databases I create on my local machine into separate groups?

Working in a home LAN, no one else is able to reach this development instance. Still, pgAdmin 4 forces a login through its web interface, which is different from the credentials used to login to the actual Postgres service. In a development environment this is just a nuisance, two different logins to connect to a service. How can I disable the web login in pgAdmin 4?

I have a *.pgerd file that I want to open an view the database diagram. What free tools can I use? I also have access to IntellJ Ultimate Edition, so if anyone knows of plugins I can use, this would also be helpful. FYI : I used https://app.diagrams.net/ to open the *.pgerd file, and it appears to work (i.e. I can see the database diagram, but it looks poorly formatted). So I'm wondering if there are any better tools out there besides app.diagrams.net ?

I installed PgAdmin 4 to my MacBook Pro Sonoma version 14.4.x and once it opened I attempted to create a server or register a server and I have host name/address as localhost, port 5432, maintenance database of postgres and the username as the username of my machine, but I get an error message saying Unable to connect to server: connection failed: connection to server at 127.0.0.1 port 5432 failed: could not receive data from server: Connection refused. What could be going on?