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

Issuing Advisory Lock

Open
#972 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the traceback entry point in asyncpg/protocol/protocol.pyx and the internal query sequence containing SELECT pg_advisory_unlock_all(), CLOSE ALL, UNLISTEN *, and RESET ALL. Reproduce the reported timeout with asyncpg 0.25.0 and PostgreSQL 12.11, then determine the expected behavior and verify that the advisory-lock cleanup no longer times out.

Written by the indexing model from the issue text.

Description

  • asyncpg version: 0.25.0
  • PostgreSQL version: 12.11
  • Do you use a PostgreSQL SaaS? If so, which? Can you reproduce
    the issue with a local PostgreSQL install?
    :
  • Python version: 3.9
  • Platform: Linux
  • Do you use pgbouncer?: No
  • Did you install asyncpg with pip?: yes
  • If you built asyncpg locally, which version of Cython did you use?: No
  • Can the issue be reproduced under both asyncio and
    uvloop?
    : NA

Receiving this error

asyncio.exceptions.TimeoutError
[View similar errors](https://link.datadoghq.com/apm/error-tracking?issueId=...471-da7ad0900002)

Traceback (most recent call last):
  File /usr/local/lib/python3.9/site-packages/ddtrace/contrib/asyncpg/patch.py, line 89, in _traced_query
    return await method(*args, **kwargs)
File asyncpg/protocol/protocol.pyx, line 338, in query
asyncio.exceptions.TimeoutError

Due to internal query call:
SELECT pg_advisory_unlock_all ( ) CLOSE ALL UNLISTEN * RESET ALL

Happening quite frequently

Dominant language
Python
Stars
8.1k
Forks
469
Avg merge
4d 1h
Merged PRs (30d)
14

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.