Expected Behavior
The program should function the same as it does without the New Relic wrapper, meaning the "returning" parameter should be available for the cursor object.
Steps to Reproduce
Any script that attempts to run a query using executemany with the "returning" parameter (while using the New Relic agent) will fail with the error: "CursorWrapper.executemany() got an unexpected keyword argument 'returning'."
Note: if you will remove the init of newrelic agent (first 2 rows) there won't be any issue.
Description It appears that when using the New Relic agent, the Aurora cursor is being wrapped with CursorWrapper. However, this object seems to be missing the "returning" parameter that is available in the original object, as seen here: https://www.psycopg.org/psycopg3/docs/api/cursors.html#psycopg.Cursor.executemany
executemany(query: Query, params_seq: Iterable[Params], *, returning: [bool](https://docs.python.org/3/library/functions.html#bool) = False) → [None](https://docs.python.org/3/library/constants.html#None)
Expected Behavior The program should function the same as it does without the New Relic wrapper, meaning the "returning" parameter should be available for the cursor object.
Steps to Reproduce Any script that attempts to run a query using executemany with the "returning" parameter (while using the New Relic agent) will fail with the error: "CursorWrapper.executemany() got an unexpected keyword argument 'returning'." Note: if you will remove the init of newrelic agent (first 2 rows) there won't be any issue.
Your Environment docker-image: python:3.11-slim newrelic: 9.12.0 psycopg: 3.2.1