Inside Intellij (Goland to be precise) I have configured two database connections - one to postgres 12.10, another to 12.8. Both have worked perfectly up until 30 minutes ago.
The 12.8 connection, when trying to do anything with it, communicates this error:
DBMS:
Case sensitivity: plain=mixed, delimited=exact
Driver: (ver. , JDBC)
Effective version: PostgreSQL (ver. 0.0)
[XX000] FATAL: type 700 not supported as catcache key.
I have tried looking up this problem but the Internet has absolutely nothing to offer on it.
I would like to hear any ideas on how to if not solve, but sidestep this problem. I have tried removing the connection and creating a new one, identical to the deleted one. Didn't help.
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 worked on pgadmin 4 and QGIS in localhost port 5432 with version 13 of PostgreSQL creating and updating table in a spatial database. I installed PostgreSQL 14 a few days ago but finally I was not using it, I worked only on PostgreSQL 13 database. So, today, I decided to uninstall PostgreSQL 14. However, after that, I lose all tables and data I've done until then on the database in PostgreSQL 13 and I don't know why because I let PostgreSQL 13 and uninstall only version 14. I cannot access to my work in QGIS as well. Can anybody help me to understand what's happened and is it possible to get back my work and how?
I still have the folder called data from PostgreSQL 13 and 14 in OS. I would like to know if it's possible to extract tables I have done before uninstallation from the data folders of PostgreSQL 14, with files in base.
Postgres data folders
base folder
Thank you if anyone can tell me and how if it's possible.
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 have 2 cloud servers of postgresql, 1st one is working fine but in second after 30 mins i am not able to connect from java application. When i connect from pgadmin it shows 30 to 40 connection and after killing those connection every thing runs smooth.
its
configuration:
postgresql/9.3
max_connections = 100
shared_buffers = 4GB
When same application is connect to other postgresql with same schema every thing works fine forever
Configuration:
postgresql/9.1
max_connections = 100
shared_buffers = 32MB
Can u please help me to understand or fix the issue
I work on a PostgreSQL 9.3 instance with hundreds of open connections. I concur to you that the open connections themselves shouldn't be a problem. Sine we don't have much information, what follows is a description of how to get started troubleshooting.
Check server logs for anything wrong. Maybe there is an issue on the OS level with initiating connections?
Try logging in with psql as the application user. Does the problem persist? If not, the problem is not with PostgreSQL. I would take a closer look at the Java code and see if something is happening there.
Note that psql and other libpq actions may not give you the full picture. Try connecting locally over a non-SSL connection while watching a packet capture. You can find (and look up) the SQLSTATE error of the connection in this case. This is because, for legacy and backwards compatibility reasons libpq does not pass the sqlstate up to the client app when connecting to the database.
My bet though is that this is not a postgresql issue. It may be an operating system issue. It may be a resource issue. It may be a client application issue.