Thread: How to get updated psycopg2 library with pgAdmin
We are facing a lot of issues with the 64 bit OID bug in psycopg2, as described here: https://github.com/psycopg/psycopg2/issues/961
I understand this fix has been released, but we cannot seem to figure out how to get the latest version of psycopg2 packaged with pgAdmin. Even installing the latest version, we still face the bug.
Is there any general guidance on how to get the latest version of psycopg2 to work with pgAdmin on both Mac and Windows?
Thank you!!
Thank you!!
Jeremy Finzel
Database Administrator Tech Lead
M 630-777-4520
Hi
On Mon, Nov 18, 2019 at 5:32 PM Finzel, Jeremy <jfinzel@enova.com> wrote:
We are facing a lot of issues with the 64 bit OID bug in psycopg2, as described here: https://github.com/psycopg/psycopg2/issues/961I understand this fix has been released, but we cannot seem to figure out how to get the latest version of psycopg2 packaged with pgAdmin. Even installing the latest version, we still face the bug.Is there any general guidance on how to get the latest version of psycopg2 to work with pgAdmin on both Mac and Windows?
Our builds (those done by the pgAdmin devs themselves, i.e. Windows, macOS, Docker, Python wheel) will all pull the latest version of psycopg in their build process. Psycopg2 2.8.4 was released on October 20th, so pgAdmin 4.15 should have it, but 4.14 will not.
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Thank you for this very helpful response.
Our builds (those done by the pgAdmin devs themselves, i.e. Windows, macOS, Docker, Python wheel) will all pull the latest version of psycopg in their build process. Psycopg2 2.8.4 was released on October 20th, so pgAdmin 4.15 should have it, but 4.14 will not.
Perfect. This is what we are seeing now. People upgrading to 4.15 are no longer experiencing the issue, whereas they still were with 4.14. Thank you for the work!!!!
Thanks,
Jeremy