There is significant discussion about using asyncpg with pgbouncer (and SQLAlchemy), e.g.
#837 and
sqlalchemy/sqlalchemy#6467

However, the majority of that discussion took place before PgBouncer 1.21 was released, which included support for prepared statements in transaction mode.

My question is, when running a new version of pgbouncer, what steps are still recommended to take? Are these suggestions still relevant?

• Should we use prepared_statement_name_func to avoid duplicate prepared statement names?
• Should we set server_reset_query_always ?
• Should we set statement_cache_size=0 ?
• Should we use NullPool?
• Anything else I missed?

Thank you