MagicStack / MagicStack/asyncpg
Temporary tables still visible after releasing connection to pool
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.1k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
It seems like releasing a connection back to the pool doesn't entirely reset its state in a way that makes it brand new for the next user. Is it expected that temporary tables are still visible? Temporary tables in PostgreSQL are dropped after the session exits but wondering if there is a missing incantation in Connection.reset() that will allow it to be reused.
import asyncio
import asyncpg
async def main():
pool = await asyncpg.create_pool(
...
min_size=1,
max_size=1,
)
async with pool.acquire() as conn:
await conn.execute("CREATE TEMPORARY TABLE foo(id INT PRIMARY KEY)")
async with pool.acquire() as conn:
await conn.execute("CREATE TEMPORARY TABLE foo(id INT PRIMARY KEY)") # DuplicateTableException
asyncio.run(main())
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 running the supplied asyncio reproduction with a one-connection pool, then inspect Connection.reset() and the pool acquire/release path. Determine whether releasing a connection should remove the temporary table, and make the behavior match the documented pool-reset expectations, with the reproduction serving as the completion check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100