MagicStack / MagicStack/asyncpg
Connection methods does not accept classic nor unusual arguments supported in other pgsql connection solution
- Dominant language
- Python
- Stars
- 8.1k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
While trying to configure a Cockroach DB cluster async connection, there seems to be missing support for usual PostgreSQL parameters (or renamed) or supported options not frequently used.
I don't know why the connection part does not seems to follow other library but it would be nice to at least support all options existing in postgresql client (even renamed ^^).
For example, the part I am missing to connect is `options` keyword. It is used to provide complementary informations on the connection (in my case a cluster id to identify exact connection). Guess it is not mandatory by itself but it fells strange to have the issue only on asyncpg :/
* **asyncpg version**: Version: 0.26.0
* **PostgreSQL version**:
* **Do you use a PostgreSQL SaaS? If so, which? Can you reproduce
the issue with a local PostgreSQL install?**: Cockroach Cloud
* **Python version**: 3.10.7 (venv)
* **Platform**: Linux (Docker VSCode python dev container)
* **Do you use pgbouncer?**: No
* **Did you install asyncpg with pip?**: Yes (using setuptools)
* **If you built asyncpg locally, which version of Cython did you use?**:
* **Can the issue be reproduced under both asyncio and
[uvloop](https://github.com/magicstack/uvloop)?**:
Contributor guide
No contributing guide indexed for this repository
Research direction
The report names asyncpg connection methods and the PostgreSQL client’s options parameter, but no repository file or test. Start by locating the connection entry point and comparing its accepted arguments with PostgreSQL options. Define the supported scope before implementation; done means the requested connection option is accepted and covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100