Hello @krishna-holvi, the problem seems legitimate but just like any non-trivial bug fixing this will require a ticket as well as tests.

See 4a1150b to get an idea for where the tests should be added. It might also be an opportunity to change the logging.error(exc_info=True) calls to logger.exception instead as the latter is an alias for the former.

Hello @krishna-holvi, the problem seems legitimate but just like any non-trivial bug fixing this will require a ticket as well as tests.

See 4a1150b to get an idea for where the tests should be added. It might also be an opportunity to change the logging.error(exc_info=True) calls to logger.exception instead as the latter is an alias for the former.

Many thanks for having a look and thank you for those links. I'll update the PR

Looks like it caused a few failures

See

• https://djangoci.com/job/pull-requests-pg-server-side-binding/database=postgres,label=focal-pr,python=python3.13/13313/
• https://github.com/django/django/actions/runs/15976880765/job/45061586865?pr=19609

Try running this particular suite locally

Updated with simplified approach as discussed in ticket. thank you!

@charettes tests are passing now, can you please have a look

📊 Coverage Report for Changed Files

-------------
Diff Coverage
Diff: origin/main...HEAD, staged and unstaged changes
-------------
django/db/backends/base/base.py (100%)
django/test/testcases.py (100%)
-------------
Total:   6 lines
Missing: 0 lines
Coverage: 100%
-------------

Note: Missing lines are warnings only. Some lines may not be covered by SQLite tests as they are database-specific.

For more information about code coverage on pull requests, see the contributing documentation.

Looks really good. Can I ask you to give one last thought to a possible third test, and let me know whether it's feasible. Thanks.

@jacobtylerwalls Thanks for the thorough review! I think I've addressed both suggestions, please let me know if there's anything else that needs adjustment.