-
Notifications
You must be signed in to change notification settings - Fork 222
Simplest query takes 30+ seconds when move from anorm to postgresql-async #212
Comments
@tpraizler can you provide a self contained example that shows this behavior? without an example database it's really hard to understand what's going on. |
I am working on it. creating a repo and application on heroku for this. Just to make sure. what do you need? |
@mauricio So I manage to focus the problem a little (can't believe I just tested it now). |
@tpraizler there shouldn't be an issue with prepared statements, were you able to setup a database that fails to execute it? A simple .sql file with code that breaks would be really useful. |
@mauricio ok. problem solved. but maybe with your help I will understand the logic behind it. My question is why prepared statement got stuck while regular query worked perfectly. Thanks! |
@tpraizler shouldn't be, there's only one way to setup prepared statements on a table so anything that sets up prepared statements should cause the same issue to happen. |
I fixed/reverted this in jasync-sql(fork) 0.8.30: jasync-sql/jasync-sql#16 . more details in the issue: jasync-sql/jasync-sql#15 |
Hey,
I am not sure if this is the right place for this, but I am hopeless. need your help!
I am trying to move my app to postgresql-async from anorm, and encountered a major problem on the first refactor.
I changed one of my daos, to be fully async using postgresql-async.
This is a message I get from postgres:
[PURPLE] duration: 41353.017 ms execute 1/1: DELETE FROM audit_log WHERE company_id = $1 Detail: parameters: $1 = '30'
This delete is basically doing nothing, I tested it on an empty set.
With anorm it work perfectly, but when move to postgresql-async, it takes 30 -40 seconds.
This is even when there is nothing to delete.
I configured the connection as follow:
Do have an idea what is missing?
Have you encounter such behavior?
Do you have any suggestion to how to approch this?
Thank you very much!
The text was updated successfully, but these errors were encountered: