I know that pgAdmin3 is now obsolete, but I still perfer it to pgAdmin4.
It was working fine up to PostgreSQL 9.* version, but when I try to connect to PostgreSQL 10 database I get:
Is there any workaround for this, or is this truly the end of pgAdmin III?
The official pgAdmin3 has issues with PgSQL 10 and is no longer being developed, but there is a fork available at https://www.openscg.com/bigsql/pgadmin3/ which does work, and will continue to receive updates.
Related
I am hosting a PostgreSQL 9.5 database on a DigitalOcean Droplet. I am using pgAdmin 4 v6.14 to access the database server.
Since upgrading to Windows 11, I still can connect and manually query the databases, but if I try to open /Schemas/public/Tables, there is just an endless "Windows-Sweep-Waiting-Icon" without any result nor error message. Other subsections such as Sequences are seemingly working fine. Other stakeholders using Windows 11 are experiencing the same issue, while users using Windows 10 can still use pgAdmin to access the database tables.
Are there any experiences with this problem? Is "just upgrade your postgreSQL version" the way to go? I am unexperienced in hosting a postgreSQL server and since there are multiple projects currently running, I am afraid to mess up with the server while it is "basically" working, and Windows 11 seems to be the discriminant factor.
Best regards
I had Postgresql 9.6 installed (on Windows 10) and did a complete uninstall including the data directory and all old copies of PgAdmin and there are no environment variables relating to this or any other old Postgres installation either.
I recently installed Postgresql 11 and PgAdmin 4 v3.6 using EnterpriseDB installer. When I run PgAdmin 4 it aurto detects a postgresql instance called 9.6 - though the details tell me it is actually my v11 instance with the same port number and password etc. The only difference is that it is pointing to the non-existent old data directory.
I have searched for a stray postgresql.conf file (and can't find one as it was in the deleted data directory!). As there is also no environment variables, no binaries and no data I can't understand how PgAdmin is auto detecting this ghost. Any suggestions on how to correct it?
EDIT:
I have tried deleting all cookies relating to PgAdmin and Postgresql in Chrome too - this had no effect
I have also double checked that there is no postgresql 9.6 service running (but that just confirms the above where PgAdmin tells me it is called 9.6 but actually is a v11 instance)
Try deleting pgAdmin4 config file pgadmin4.db located at %APPDATA%\pgAdmin\
Restart pgAdmin4 and check.
I need to use the new jsonb field in postgres so I decided to upgrade to 9.5 in my ununtu 16.04 LTS. I followed this tutorial , but when it gets to the command pg_upgradecluster 9.3 main, I get the error that cluster configuration already exists. I checked other tutorials and found that I could get the list of clusters with pg_lsclusters. But the command always shows only the 9.3 cluster. Any attempt to create the 9.5 cluster always results to cluster configuration already exists. I purged the 9.5 and installed again multiple times but the same result. At last I decided to purge all the postgres installations I have after backing up my 9.3 cluster with pg_dumpall.
Now I have decided to install the 9.5 freshly but I still get the same thing. When I install pg_lsclusters shows nothing and after starting postgres psql always returns psql: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
Right now I'm so tired and frustrated. Please if anyone has any possible solution or suggestion, help
The problem seemed to be from the version 9.5 in the postgres repositories. I installed 9.6 and everything worked like magic. Had I known there was a stable 9.6 earlier, I wouldn't have wasted 6 hours of my life in something I could have done for 10 minutes. Anyway, I'm happy I have have a working postgres with jsonb field
I am fairly new to Rails and especially Heroku. I received an email informing me that I needed to update my PostgreSQL DB version. I am a little fuzzy on how to accomplish this without changing my plan. I am currently using Heroku's Kappa Postgres plan. Based on what I am reading here:
https://devcenter.heroku.com/articles/upgrade-heroku-postgres-with-pgbackups
Should I use the command:
heroku addons:add heroku-postgresql:kappa --version 9.3
And then just continue on as instructed?
Just doing this myself, from 9.2.4 databases ...
You don't have to upgrade to 9.3, you can just create a new 9.2 and it will be 9.2.6, in which the issue you're being notified about has been fixed. However if you go to 9.3 the plans are different -- https://devcenter.heroku.com/articles/heroku-postgres-plans#standard-tier
It's more simple/safe to upgrade with a follower database. Instructions here, although you probably want to add your app name to most of those commands. https://devcenter.heroku.com/articles/heroku-postgres-follower-databases#database-upgrades-and-migrations-with-changeovers
I'm having some problems with replication in pgAdmin. It says:
Slony creation scripts not available.
I use File > Options and indicate the path "usr/share/slony" where I suppose they are. Because that directory has xxid.v80.sql and all of them.
My problem is, pgAdmin still doesn't recognize the creation scripts for the cluster.
My setup: SO-Ubuntu, pgAdmin, PostgreSQL 8.4
Any ideas?
for some reason version 1.2 of slony has some troubles with pgadmin3 1.10 or postgres 8.4 (That's what I asume). I just uninstalled version of slony from sinaptyc and installed slony v2.0.6 from source (slony1.tar.bz2) and everything worked fine for postgres 8.4
Hope this helps,