pgAdmin 4: Cannot open public schema "Tables" after upgrading to Win11 - postgresql

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

Related

Stymied by idle_in_transaction_session_timeout

Immediate problem: When I do a pgAdmin 4 restore I get "Stymied by idle_in_transaction_session_timeout" error.
I am on a MacBook Pro running macOS Mojave version 10.14.5, using Java and PostgreSQL. I use the pgAdmin 4 GUI, as I am not proficient in psql, bash, etc. I have a test database named pg2. As you can see from the attachment, PostgreSQL servers 9.4 and 10 have the identical databases. If I make a change in a database on one server, it will show also in the other server’s database. There is a third server, 11, in which there is only the postgres database.
I have tried psql and get errors (including timeout errors).
I have tried to Delete/Drop server 11, it will disappear but when I sign out of pgAdmin 4 and then go into pgAdmin 4 again the server 11 will be there again.
See the attachments for screen shots.
I expect the backup/restore to work: backup, then make a change to the database, then correctly restore to previous state.
I would like to have just one server, preferably 11 with only pg1 and the test db tempdb running in it. I thought that I could live with the three, for I am aware of my current capabilities and thus did not want to screw things up further. However, I suspect that the two servers 9.4 and 10 are the source of my current problem: receiving the idle_in_transaction_session_timeout error while doing a restore. Note: I did the backup using the server 10’s pg1 backup. Did it create 2 backups, one for 9.4 and one for 10?
I tried to attach these before. They will help make sense of my problem.
The 2 servers have the same database; is this causing the idle in transaction session timeout?

How to connect to postgresql 10+ database with pgAdmin 3?

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.

MSDTC and Windows Server 2008 Error

I have an application server and a DB server, both with Windows Server 2008 R2 and SQL Server 2008 R2, I have a C# application installed and 2 databases (my application was developed using Framework 2.0), I use TransactionScope for Insert, Update and Delete, everything is fine when I execute any of those operations in just 1 db but the problem comes if I work with the 2 databases at the same time, I don't have this problem installing the application and the databases in the same Server. I already configured MSDTC in both servers but I can't solve this error, by the way, I have the firewall turned on, I don't know if this is causing me any conflict.
I hope you can help me.
Thank you so mucho and have a nice day/night.
PS: I appologize for my english.

How to enable SSL for postgres connections for Heroku on Tableau Mac version?

There is currently no way to enable SSL connections with a PostgreSQL connection on tableau's 8.2 version for Mac OSX. It used to be that you could create a generic ODBC and turn SSL as described here:
http://kb.tableausoftware.com/articles/howto/connect-to-postgresql-using-ssl-on-non-standard-port
Now there is no ODBC connections and PostgreSQL only has the following options:
Has anyone solved for this problem with the Mac Tableau version with Heroku Postgres?
This may not be a great long term answer, and doesn't answer your exact question, but might be a viable workaround if you haven't considered it:
You can use the Tableau data extract API to connect via SSL, read the info you need and create a Tableau extract. Then you can connect to the extract via a mac, and rerun your program on a schedule to refresh the extract periodically. You may even see a nice performance improvement, at the expense of not reading live up to the minute updates.
Then you can replace the extract connection with a live one, once Tableau improves their PostgreSQL driver to support SSL from macs.

how to connect redshift cluster using tableau 8.0 desktop

I have downloaded Tabeleau 8.0.1 desktop version. I am able to connect my local postgres database through tableau.
But when I try to connect to the redshift cluster, I am getting an error - invlaid userid /password. I already have passed userid and password correctly. FYI, I am able to connect redshift through sqlworkbench/j, command line prompt (psql) & pgadmin III. And I already have downlaoded the redshift driver as per http://www.tableausoftware.com/support/drivers.
However I am not able to connect redshift cluster through tableau.
Amazon Redshift has a direct connect with Tableau. When you start Tableau, please use the Connect to Data option and then choose Amazon Redshift on the left. You'll see the following log-in screen. You shouldn't need to worry about drivers. Also, the Tableau trial version is the full version, so there is no limiting of features.
You can read more here, and watch a video. Also technical details are here. You may want to try version 8.1, which is the most recent version (also has 64 bit)