Bold claim, since psycopg2 is used overwhelmingly more than any other library. Though asyncpg (or something like it) is likely the future, it’s a long way to go before calling psycopg obsolete.

Asyncpg is not future, it is present. We use it in production and quite happy with it.

That still doesn't really challenge parent's claims.

If asyncpg is qualitatively better across the board and psycopg2 is only being used preferentially due to historical precedence, I'd say calling it obsolete is fair.

Doesn't asyncpg require asyncio? That's a fairly niche market, especially given the alternative async libraries even in that space (twisted, trio). Why would it be faster anyway, on a use case like this?