asyncpg icon indicating copy to clipboard operation
asyncpg copied to clipboard

A fast PostgreSQL Database Client Library for Python/asyncio.

Results 213 asyncpg issues
Sort by recently updated
recently updated
newest added

EDIT: nvm, looks like there's really no mechanism in the pgwire protocol that would support this behavior. Would it at all be possible to support prefetching a batch of up...

Not sure if i'm better asking this on the [cloud sql python connector repo](https://github.com/GoogleCloudPlatform/cloud-sql-python-connector) or here, but I'm trying to understand how to effectively call `asyncpg.create_pool(...)` but make it work...

* **asyncpg version**:.29.0 * **PostgreSQL version**: 2.0.26 * **Do you use a PostgreSQL SaaS? If so, which? Can you reproduce the issue with a local PostgreSQL install?**: no * **Python...

* **asyncpg version**: 0.29.0 * **PostgreSQL version**: 14.9 * **Do you use a PostgreSQL SaaS? If so, which? Can you reproduce the issue with a local PostgreSQL install?**: no *...

* **asyncpg version**: 0.29.0 * **PostgreSQL version**: 15.6 * **Python version**: 3.11.4 * **Platform**: debian * **Do you use pgbouncer?**: no * **Did you install asyncpg with pip?**: yes *...

The default connection reset behaviour might be an overkill for some cases e.g. when respective server capabilities are not used or resources are cleaned up explicitly before returning the connection...

* **asyncpg version**: 0.29.0 * **PostgreSQL version**: 15.6 * **Do you use a PostgreSQL SaaS? If so, which? Can you reproduce the issue with a local PostgreSQL install?**: No *...

* **asyncpg version**: 0.29.0 * **PostgreSQL version**: 16 * **Do you use a PostgreSQL SaaS? If so, which? Can you reproduce the issue with a local PostgreSQL install?**: * **Python...

* **asyncpg version**: 0.29.0 * **PostgreSQL version**: PostgreSQL 15.5 (Debian 15.5-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit * **Do you use a PostgreSQL SaaS? If so, which?...

libpq has support for something called asynchronous command processing (https://www.postgresql.org/docs/current/libpq-async.html). Thea idea is fairly simple: you can queue up multiple queries on one connection without waiting for the previous result...