Skip to content

Requirements: use psycopg3 #10667

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 1, 2023
Merged

Requirements: use psycopg3 #10667

merged 1 commit into from
Sep 1, 2023

Conversation

humitos
Copy link
Member

@humitos humitos commented Aug 26, 2023

Now we are on Django 4.2 we can use the latest version of psycopg.

Closes #10596

Now we are on Django 4.2 we can use the latest version of psycopg.

Closes #10596
@humitos humitos requested a review from a team as a code owner August 26, 2023 17:48
@humitos humitos requested a review from stsewd August 26, 2023 17:48
@humitos
Copy link
Member Author

humitos commented Sep 1, 2023

I'm merging this. If something fails we will notice it immediately when deploying web-extra

@humitos humitos merged commit 4e6d299 into main Sep 1, 2023
@humitos humitos deleted the humitos/requirements-psycopg3 branch September 1, 2023 20:09
humitos added a commit that referenced this pull request Sep 5, 2023
This package works fine and the upgrade was transparent. However, it seems that
New Relic agent is not prepared to collect data from v3.x and send it to their
servers.

https://docs.newrelic.com/docs/apm/agents/python-agent/getting-started/instrumented-python-packages/#instance-details

> The Python agent should be able to track database queries for any Python
> DB-API 2.0 compliant modules

`psycopg3` is compatible with DB-API 2.0, but for some reason doesn't work.
I'm reverting it for now and we can take a look later.

Note this commit also upgrades Django, due to a security issue that was
reported:

https://docs.djangoproject.com/en/4.2/releases/4.2.5/

Reverts #10667
humitos added a commit that referenced this pull request Sep 5, 2023
This package works fine and the upgrade was transparent. However, it seems that
New Relic agent is not prepared to collect data from v3.x and send it to their
servers.

https://docs.newrelic.com/docs/apm/agents/python-agent/getting-started/instrumented-python-packages/#instance-details

> The Python agent should be able to track database queries for any Python
> DB-API 2.0 compliant modules

`psycopg3` is compatible with DB-API 2.0, but for some reason doesn't work.
I'm reverting it for now and we can take a look later.

Note this commit also upgrades Django, due to a security issue that was
reported:

https://docs.djangoproject.com/en/4.2/releases/4.2.5/

Reverts #10667
humitos added a commit that referenced this pull request Sep 5, 2023
This package works fine and the upgrade was transparent. However, it seems that
New Relic agent is not prepared to collect data from v3.x and send it to their
servers.

https://docs.newrelic.com/docs/apm/agents/python-agent/getting-started/instrumented-python-packages/#instance-details

> The Python agent should be able to track database queries for any Python
> DB-API 2.0 compliant modules

`psycopg3` is compatible with DB-API 2.0, but for some reason doesn't work.
I'm reverting it for now and we can take a look later.

Note this commit also upgrades Django, due to a security issue that was
reported:

https://docs.djangoproject.com/en/4.2/releases/4.2.5/

Reverts #10667
humitos added a commit that referenced this pull request Sep 12, 2023
* Requirements: revert upgrade to `psycopg==3.x`

This package works fine and the upgrade was transparent. However, it seems that
New Relic agent is not prepared to collect data from v3.x and send it to their
servers.

https://docs.newrelic.com/docs/apm/agents/python-agent/getting-started/instrumented-python-packages/#instance-details

> The Python agent should be able to track database queries for any Python
> DB-API 2.0 compliant modules

`psycopg3` is compatible with DB-API 2.0, but for some reason doesn't work.
I'm reverting it for now and we can take a look later.

Note this commit also upgrades Django, due to a security issue that was
reported:

https://docs.djangoproject.com/en/4.2/releases/4.2.5/

Reverts #10667

* Update packages
humitos added a commit that referenced this pull request Jun 20, 2024
We attempt to upgrade this some time ago (in #10667) but we reverted it later
since New Relic Python client wasn't compatible with it.

The newer version of New Relic that we are already using added compatibility and
should log database transactions properly now.

Closes #10596
humitos added a commit that referenced this pull request Jun 20, 2024
We attempt to upgrade this some time ago (in #10667) but we reverted it later
since New Relic Python client wasn't compatible with it.

The newer version of New Relic that we are already using added compatibility and
should log database transactions properly now.

Closes #10596
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Requirement: upgrade psycopg to version 3.1.8 or higher
2 participants