django-pgtrigger VS asyncpg

Compare django-pgtrigger vs asyncpg and see what are their differences.


Write Postgres triggers for your Django models (by Opus10)


A fast PostgreSQL Database Client Library for Python/asyncio. (by MagicStack)
Our great sponsors
  • InfluxDB - Build time-series-based applications quickly and at scale.
  • Sonar - Write Clean Python Code. Always.
  • SaaSHub - Software Alternatives and Reviews
django-pgtrigger asyncpg
2 9
383 5,818
5.7% 1.0%
8.7 5.3
3 months ago 8 days ago
Python Python
GNU General Public License v3.0 or later Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of django-pgtrigger. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-09-02.
  • This Week in Python
    4 projects | | 2 Sep 2022
    django-pgtrigger – Write Postgres triggers for your Django models
  • A lightweight alternative to Celery for Django-PostgreSQL apps.
    2 projects | | 25 May 2022
    Note that have now ditched our post_save signal from the previous solution. As we pointed out, signals can easily be missed. Instead, we are using a Postgres trigger : defining the listener as it is above makes use of the django-pgtrigger library to write a Postgres trigger to our database, the job of which is to notify our channel whenever a Comment is inserted in to the database. Triggers are far more robust than signals for detecting database write events; application level triggers can easily be missed, whereas triggers will always be executed.


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 2022-06-28.
  • aiopg vs asyncpg vs psycopg3
    3 projects | | 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 | | 12 Apr 2022
    Quart-DB uses asyncpg to manage the connections and buildpg to parse the named parameter bindings.
  • 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
  • Large database to python - SQL advantageous? (mysql)
    2 projects | | 4 Oct 2021
    Highly recommend
  • Postgrey - Simple, Fast & Async Library for PostgreSQL
    2 projects | | 29 Jun 2021
    🐘 Simple, Fast, Async & ORM PostgreSQL database client based on Asyncpg for Python.
  • New major versions of Flask, Jinja, Click, and Werkzeug released!
    9 projects | | 11 May 2021
    What we get with the async part of this release - If you would like to run an async library or your own async code from a flask route you can do that now. This is super useful, where let's say we have some async code that fetches data from many sources concurrently, or call multiple a few ML prediction endpoints at the same time (as long as they don't time out) using httpx and respond with some sort of outcome, or finally try that cool new async-only database library. A current (v2) limitation is that the you can't make concurrent requests using just the current asyncio implementation (an alternative with Flask API and ASGI: Quart). Typically in production gunicorn or uwsgi + threads/processes/gevent-eventlet is used and this makes Flask behave asynchronously. More here and here if interested.
  • Migrating to SQLAlchemy 2.0
    3 projects | | 18 Feb 2021
    Agreed. I will never recommend an ORM, things simply spiraled out of control for medium to large-ish projects that had more than 2 developers. Even with "best practices", code ended up having a mix of raw SQL and ORM-style queries, and it was hard to reason about the code.

    Since switching to asyncpg [0] these problems have vanished. It commands a deeper knowledge of actual SQL, but I would argue this knowledge is absolutely necessary and one of the disadvantages of an ORM is that it makes the SQL that is eventually run opaque.

    Not sure if there are equivalents to asyncpg for other RDBMS's.


  • Piccolo, an async query builder and ORM for Python
    4 projects | | 10 Jan 2021
    Asyncio makes a lot of sense when you want high throughput applications. Piccolo is built on top of asyncio and a fast database adapter called asyncpg. You can also use Piccolo within a traditional synchronous app too.

What are some alternatives?

When comparing django-pgtrigger and asyncpg you can also consider the following projects:

psycopg2 - PostgreSQL database adapter for the Python programming language

pymssql - Official home for the pymssql source code.

awesome-mysql - A curated list of awesome MySQL software, libraries, tools and resources

mysql-python - MySQLdb is a Python DB API-2.0 compliant library to interact with MySQL 3.23-5.1 (unofficial mirror)

aiopg - aiopg is a library for accessing a PostgreSQL database from the asyncio

PyMySQL - Pure Python MySQL Client

pgbouncer - lightweight connection pooler for PostgreSQL

PyPika - PyPika is a python SQL query builder that exposes the full richness of the SQL language using a syntax that reflects the resulting query. PyPika excels at all sorts of SQL queries but is especially useful for data analysis.

queries - PostgreSQL database access simplified

motor - Motor - the async Python driver for MongoDB and Tornado or asyncio

PyMongo - MongoDB Ecosystem Documentation

mysqlclient - MySQL database connector for Python (with Python 3 support)