Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Application Flow Stuck Unless Connection is Explicitly Closed

Open
#1,216 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
postgresql, python
Domain
backend, databases

Research direction

Start with the provided asyncpg 0.30.0 example and reproduce it on Python 3.11, PostgreSQL 16, and Windows, first confirming whether the issue occurs with a local PostgreSQL installation. Investigate the behavior of the async context manager around self.get_connection() and compare it with the explicit conn.close() case; done means the flow completes without requiring that explicit close.

Written by the indexing model from the issue text.

Description

  • asyncpg version: 0.30.0
  • PostgreSQL version: 16
  • Do you use a PostgreSQL SaaS? If so, which?: Yes, I am using NeonDB
  • Can you reproduce the issue with a local PostgreSQL install?: Didn't attempt it.
  • Python version: 3.11.0
  • Platform: Windows
  • Do you use pgbouncer?: No
  • Did you install asyncpg with pip?: Yes
  • If you built asyncpg locally, which version of Cython did you use?: [Your Cython version if applicable]
  • Can the issue be reproduced under both asyncio and
    uvloop?
    : [Yes/No] I did not try uvloop

I'm encountering an issue where the flow of my application gets stuck unless the database connection is explicitly closed after a query, even though it should be managed automatically by the context manager.

Code Example:

async def read_record(self, request_details: dict):
    """
    Retrieve records based on conditions and request_type.
    
    Args:
        request_details (dict): The conditions including request_type.
    
    Returns:
        list: The records that match the conditions.
    """
    table = self.get_table_name(request_details['request_type'])
    conditions = {key: request_details[key] for key in request_details if key != 'request_type'}
    condition_str = " AND ".join(f"{key} = ${i+1}" for i, key in enumerate(conditions.keys()))
    query = f"SELECT * FROM {table} WHERE {condition_str};"

    async with self.get_connection() as conn:
        conn.add_log_listener(lambda connection, message: logger.info("PostgreSQL log message: %s", message))
        result = await conn.fetch(query, *conditions.values())
        logger.info("Fetched records: %s", result)
        # await conn.close() # get's stuck without this line

    return result
Dominant language
Python
Stars
8.1k
Forks
469
Avg merge
2d 20h
Merged PRs (30d)
9

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MagicStack/asyncpg

All issues in MagicStack/asyncpg

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.