kimapr ☭

this is normal, right?

22:58:57.784 [info] Postgrex.Protocol (#PID<0.40128104.0>) disconnected: ** (DBConnection.ConnectionError) client #PID<0.40962400.0> exited 22:59:04.556 [info] Postgrex.Protocol (#PID<0.40126271.0>) disconnected: ** (DBConnection.ConnectionError) client #PID<0.40971756.0> exited 23:00:05.401 [info] Postgrex.Protocol (#PID<0.40125088.0>) disconnected: ** (DBConnection.ConnectionError) client #PID<0.40974771.0> exited 23:00:25.624 [info] Postgrex.Protocol (#PID<0.40118623.0>) disconnected: ** (DBConnection.ConnectionError) client #PID<0.40965528.0> exited 23:00:28.752 [info] Postgrex.Protocol (#PID<0.40117743.0>) disconnected: ** (DBConnection.ConnectionError) client #PID<0.40973532.0> exited 23:01:29.409 [info] Postgrex.Protocol (#PID<0.40126271.0>) disconnected: ** (DBConnection.ConnectionError) client #PID<0.40978713.0> exited 23:01:36.380 [info] Postgrex.Protocol (#PID<0.40118623.0>) disconnected: ** (DBConnection.ConnectionError) client #PID<0.40986627.0> exited
Apr 10 at 11:02pmWeb
Show threadserial disappointment lainApr 10
@kimapr usually this is Postgres query timeouts. For Akkoma, I had to create an index and cleanup my database using pg_repack because of dead tuples impacting query performance. I can provide some queries when I get home in 2 hours to try.
Show threadkimapr ☭Apr 10
@nop vruh !! but i set the postgres query timeout to 30 minute!!
Show threadserial disappointment lainApr 10
@kimapr the connections will also get cancelled if the HTTP requests get cancelled so nginx or something else could be closing the connections.