MagicStack / MagicStack/asyncpg
copy_records_to_table depends on prepared statments even with cache=0
Open
- Dominant language
- Python
- Stars
- 8.1k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
I have to use pg_bouncer in transaction mode, so tried disabling statement cache. However, when using copy_records_to_table, I am still getting prepared statement errors.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the copy_records_to_table entry point and inspect how cache=0 affects statement handling. Reproduce the report using pg_bouncer in transaction mode and verify whether prepared statement errors still occur; done means the operation works without those errors when statement caching is disabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100