Disconnection from postgres-compatible google cloud AlloyDB instance hangs

Open

#962 opened on Oct 5, 2022 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: Mostly clear
Activity status: Stale
Tech stack: gcp, postgresql, python
Domain: cloud, databases

Research direction

Start at the connection.disconnect() call in the provided AlloyDB-auth-proxy reproduction and run it against the reported Google Cloud AlloyDB setup. Compare the behavior with a local PostgreSQL installation and the existing psycopg2 behavior; done means identifying the cause of the hang and ensuring asyncpg disconnects cleanly for this setup.

Written by the indexing model from the issue text.

Description

asyncpg version: 0.26.0
PostgreSQL version: Google AlloyDB, postgres 14.4 compatible
Do you use a PostgreSQL SaaS? If so, which? Can you reproduce
the issue with a local PostgreSQL install?: I cannot reproduce the issue on a local postgres, no.
Python version: 3.10
Platform: Macos
Do you use pgbouncer?: No
Did you install asyncpg with pip?: Yes
If you built asyncpg locally, which version of Cython did you use?: NA
Can the issue be reproduced under both asyncio and
uvloop?: I have not tried to reproduce under uvloop

I am connecting to an AlloyDB instance on Google Cloud (currently, these are available for free testing). I can connect and queries run as expected. However, connection.disconnect() hangs. I cannot reproduce this behavior locally; disconnection happens as expected. Synchronous database work with psycopg2, for example, works as expected.

This code reproduces the behavior I am seeing (running through the alloydb-auth-proxy as is required):

import asyncpg
conn = await asyncpg.connect(ALLOYDB_URI)
conn.disconnect() # hangs

I'll put in a ticket with Google as well if nothing obvious turns up here.

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

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.

Similar issues

[Bug] reef-hermes tells me to resume with hermes --resume, which does not work from my shell Open

area: harness bug status: needs-triage

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

Human-Agent-Society/reef#625 · Opened Sep 24, 2026
Bump transitive axios to >=1.18.0 to address GHSA-hcpx-6fm6-wx23 Open

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

coinbase/cdp-sdk#828 · Opened Sep 24, 2026
AccessibleResourceCard/AccessibleChannelCard crash when a resource has more than one learning activity (getActivityTags returns an object instead of an array) Open

Difficulty 1/5 Under an hour Newbie friendliness 80/100

learningequality/kolibri#15351 · 2 comments · Opened Sep 24, 2026
audeer.path(): optionally expand environment variables Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

audeering/audeer#212 · 1 comment · Opened Sep 24, 2026
Name consistency Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

eellak/triplestore#65 · 1 comment · Opened Sep 24, 2026

More Python issues