Postgres Pro
Downloads
Home   >   mailing lists

Re: Skipping pgAdmin 4 release for March and planning a major release v7.0 in April - Mailing list pgadmin-support

From Khushboo Vashi
Subject Re: Skipping pgAdmin 4 release for March and planning a major release v7.0 in April
Date
Msg-id CAFOhELce5FJyq4DLPkTUGsQeX2x==nsha82R1A9vxDqECF7DLA@mail.gmail.com
Whole thread Raw
In response to Skipping pgAdmin 4 release for March and planning a major release v7.0 in April  (Akshay Joshi <akshay.joshi@enterprisedb.com>)
List pgadmin-support
Tree view

Hi,

On Wed, Mar 1, 2023 at 6:52 PM Akshay Joshi <akshay.joshi@enterprisedb.com> wrote:


---------- Forwarded message ---------
From: Elvia Gomez <egomez@amps.com>
Date: Wed, Mar 1, 2023 at 6:29 PM
Subject: Re: Skipping pgAdmin 4 release for March and planning a major release v7.0 in April
To: Akshay Joshi <akshay.joshi@enterprisedb.com>, pgAdmin Support <pgadmin-support@postgresql.org>


Since upgrade to 6.20, in Azure VM, PgAdmin is connecting too many times to be counted to all databases existent in the Azure database cluster, maybe like trying a heart-bit. We are able to see it happening because of permission denied errors as the ones below without humanly possible to try many attempts within a second:

pgAdmin sends heartbeat to the server for only connected PG servers to get rid of orphan databases. Your error logs says the user doesn't have connect privileges,
so if the database is not connected, pgAdmin will not send heartbeat. Do you have any reproduction steps or scenarios for this ? It will help us to fix the issue.

By default pgAdmin sends a heartbeat every 30 seconds per server, which you can change by configuring SERVER_HEARTBEAT_TIMEOUT = <required_seconds>.
Refer https://www.pgadmin.org/docs/pgadmin4/6.20/config_py.html to set the configuration parameter.

Thanks,
Khushboo

 

Regards,

 

Elvia M Gomez

cidimage001.png@01D71976.70950A50

 

This message may contain confidential or proprietary information intended only for the use of the addressee(s) named above or may contain information that is legally privileged. If you are not the intended addressee, or the person responsible for delivering it to the intended addressee, you are hereby notified that reading, disseminating, distributing or copying this message is strictly prohibited. If you have received this message by mistake, please immediately notify us by replying to the message and delete the original message and any copies immediately thereafter. Thank you.

 

 

From: Akshay Joshi <akshay.joshi@enterprisedb.com>
Date: Tuesday, February 28, 2023 at 5:14 AM
To: pgAdmin Support <pgadmin-support@postgresql.org>
Subject: Skipping pgAdmin 4 release for March and planning a major release v7.0 in April

 

Hi All

 

We plan to support/upgrade the following packages: 

  1. Psycopg3
  2. Support for Psycopg2 will be removed (*If and only if* Python 3.6 support will be removed)
  3. Support for Python 3.6 will be removed (still under investigation. Evaluating support for CentOS 7, Ubuntu 18)
  4. Flask
  5. SQLAlchemy
  6. Flask-SQLAlchemy
  7. Werkzeug

The next big release of pgAdmin 4 will be v7.0 with all the changes listed above, so we are skipping the March release and will release it in April.

Attachment

pgadmin-support by date:

Previous
From: Akshay Joshi
Date:
Subject: Re: Skipping pgAdmin 4 release for March and planning a major release v7.0 in April
Next
From: Natalia Merkulova
Date:
Subject: The dashboard is gone