MagicStack / MagicStack/asyncpg
FAQ, statement_cache_size=0...
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.1k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
I have done a create_pool, passing the argument 'statement_cache_size=0"; I am STILL _periodically_ getting the DuplicatePreparedStatement error on statements prepared from a connection acquired from that pool.
Any other options? All other facilities appear to work reliably in your driver except this critically important prepared statement facility.
Running your latest driver, postgres 12; application is running in the context of a uwsgi server app. Connecting via a socket file (in /var/run...) to postgres...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the create_pool configuration with statement_cache_size=0 in a uwsgi application against PostgreSQL 12 over a Unix socket. Investigate when connections acquired from the pool still produce DuplicatePreparedStatement errors; done means the reported periodic error is reproduced and its cause or a reliable resolution is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100