You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A very commonly used Python library for Posgres is bundling their own libssl https://www.psycopg.org/docs/install.html. We should look harder for the libssl symbols to add our UProbes.
The text was updated successfully, but these errors were encountered:
After some initial investigation it seems that the recommended approach for psycopg2 is to use the no-binary distribution (which bundles their older version of libssl 1.1). https://www.psycopg.org/docs/install.html
The psycopg vs psycopg-binary section says:
The psycopg2-binary package is meant for beginners to start playing with Python and PostgreSQL without the need to meet the build requirements.
If you are the maintainer of a published package depending on psycopg2 you shouldn’t use psycopg2-binary as a module dependency. For production use you are advised to use the source distribution.
I tested our examples code with Potgresql with SSL mode and with installing psycopg2 from source, e.g. pip install psycopg2 and it picks up my local libssl3 and Beyla is able to correlate the events.
A very commonly used Python library for Posgres is bundling their own libssl https://www.psycopg.org/docs/install.html. We should look harder for the libssl symbols to add our UProbes.
The text was updated successfully, but these errors were encountered: