Skip to content

ayncpg error message #2325

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
liquidsec opened this issue Mar 1, 2025 · 3 comments
Closed

ayncpg error message #2325

liquidsec opened this issue Mar 1, 2025 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@liquidsec
Copy link
Collaborator

Periodically receiving this in stdout. Looks like its coming from crt module

[INFO] crt: Error retrieving results for upsells.boldapps.net: prepared statement "__asyncpg_stmt_1__" does not exist
HINT:  
NOTE: pgbouncer with pool_mode set to "transaction" or
"statement" does not support prepared statements properly.
You have two options:

* if you are using pgbouncer for connection pooling to a
  single server, switch to the connection pool functionality
  provided by asyncpg, it is a much better option for this
  purpose;

* if you have no option of avoiding the use of pgbouncer,
  then you can set statement_cache_size to 0 when creating
  the asyncpg connection object.

@liquidsec liquidsec added the bug Something isn't working label Mar 1, 2025
@liquidsec
Copy link
Collaborator Author

Image

@TheTechromancer
Copy link
Collaborator

Yeah I think the postgres method is not reliable at all. I was hitting rate limits this morning

@TheTechromancer
Copy link
Collaborator

Fixed in #2373.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants