You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
flask-profiler is awesome, nice work! I'm using it with SQLAlchemy and PostgreSQL. Sometimes there are spikes of usage with my app though, and I get this error:
which I believe is an error writing the runtime to PostgreSQL occurring when there's many simultaneous database connections. Perhaps flask-profiler could fix this error, by adding a pool_pre_ping=True to the database engine.
Regardless if that error is fixed, I would expect that such an error doesn't also make the endpoint call fail. Couldn't flask-profiler run the "write to database" step in a subprocess that's allowed to fail so that the endpoint can still succeed?
The text was updated successfully, but these errors were encountered:
flask-profiler
is awesome, nice work! I'm using it withSQLAlchemy
and PostgreSQL. Sometimes there are spikes of usage with my app though, and I get this error:which I believe is an error writing the runtime to PostgreSQL occurring when there's many simultaneous database connections. Perhaps
flask-profiler
could fix this error, by adding apool_pre_ping=True
to the database engine.Regardless if that error is fixed, I would expect that such an error doesn't also make the endpoint call fail. Couldn't
flask-profiler
run the "write to database" step in a subprocess that's allowed to fail so that the endpoint can still succeed?The text was updated successfully, but these errors were encountered: