A fast PostgreSQL Database Client Library for Python/asyncio. (by MagicStack)

Asyncpg Alternatives

Similar projects and alternatives to asyncpg

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better asyncpg alternative or higher similarity.

asyncpg reviews and mentions

Posts with mentions or reviews of asyncpg. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-01-27.
  • Ask HN: Is Python async/await some kind of joke?
    4 projects | | 27 Jan 2024
    - SqlAlchemy/asyncpg => you can’t use it if you’re using PgBouncer (necessary most of the time with Postgres) in transaction mode? What??
  • Differences from Psycopg2
    1 project | | 10 Oct 2023
    OK I stand corrected, asyncpg has these two C files:

    If you are interested here is a post by the psycopg author about psycopg2 and 3 and performance versus asyncpg.

  • Asyncpg – A Fast PostgreSQL Database Client Library for Python/Asyncio
    1 project | | 29 Sep 2023
  • Ruby Outperforms C: Breaking the Catch-22
    4 projects | | 9 Sep 2023
    This pure Python library claims quite fabulous performance:

    I believe it because that team have done lots of great stuff but I haven't used it, I just remembered thinking it was interesting the performance was so good. Not sure how related it is to running on the asyncio loop (or which loop they used for benchmarks).

  • PgBouncer is useful, important, and fraught with peril
    2 projects | | 8 Sep 2023
    what a great post, we have had a ton of issues with users using pgbouncer and it's not because things are "broken" per se, it's just the situation is very complicated, and pgbouncer's docs are also IMO in need of updating to be more detailed and in a few critical cases less misleading, specifically the prepared statements docs.

    This blog post refers to this misleading nature at .

    > PgBouncer says it doesn’t support prepared statements in either PREPARE or protocol-level format. What it actually doesn’t support are named prepared statements in any form.

    That's also not really accurate. You can use a named prepared statement just fine in transaction mode. start a transaction (so you aren't in autocommit), use a named statement, works fine. you just can't use it again in another transaction, because it will be "gone" (more accurately, "unmoored" - might be in your session, might be in someone else's session). Making things worse, when the prepared statement is "unmoored", its name can then conflict with another client attempting to use the same name.

    so to use named prepared statements, you can less ideally name them with random strings to avoid conflicts, or you can DEALLOCATE the prepared statement(s) you used at the end of your transaction. for our users that use asyncpg, we have them use a uuid for prepared statements to avoid these name conflicts (asyncpg added this feature for us here: however, they can just as well use DEALLOCATE ALL, set this as their `server_reset_query`, and then so that happens in transaction mode, also set `server_reset_query_always`, so that it's called at the end of transactions. Where pgbouncer here IMO entirely misleadingly documents this as "This setting is for working around broken setups that run applications that use session features over a transaction-pooled PgBouncer." - which is why nobody uses it, because pgbouncer claims this is "broken". It's not any more broken than it is to switch out the PostgreSQL session underneath a connection that uses multiple transactions. Pgbouncer can do better here and make this clearer and more accommodating of real world database drivers.

  • Library to connect Python to Postgresql
    1 project | /r/learnpython | 4 May 2023
    asyncpg is another great driver if you're using asyncio and want maximum performance (although they also break with DBAPI, but the tradeoff may be worth it).
  • aiopg vs asyncpg vs psycopg3
    3 projects | /r/learnpython | 28 Jun 2022
    asyncpg: 5.5k starts, last commit recently, ~150 issues, some incompatibility, few open PRs, extensive README. Includes benchmark showing it's supposedly 3x faster than aiopg and psycopg2, psycopg3 is not mentioned in the benchmark.
  • Announcing Quart-DB
    3 projects | /r/Python | 12 Apr 2022
    Quart-DB uses asyncpg to manage the connections and buildpg to parse the named parameter bindings.
  • Should I use TimescaleDB or partitioning is enough?
    1 project | /r/PostgreSQL | 4 Mar 2022
    A major performance boost specifically on inserts with timescaledb was actually starting to use
  • Cascade of doom: JIT, and how a Postgres update led to 70% failure on a critical national service
    7 projects | | 13 Nov 2021
    Simple query runs long when DB schema contains thousands of tables #186
  • A note from our sponsor - SaaSHub | 29 May 2024
    SaaSHub helps you find the best software and product alternatives Learn more →


Basic asyncpg repo stats
27 days ago

MagicStack/asyncpg is an open source project licensed under Apache License 2.0 which is an OSI approved license.

The primary programming language of asyncpg is Python.

SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives