Generally osm2pgsql should not hold open connections for a long time and the
situation should have improved with changes in recent versions. This goes
double for sessions that have a transaction open. Open sessions use ressources
while they are open, but more importantly open transactions can lead to bloat.
I think we should first try to get the root cause solved in the application or
at least try to figure out how long we need this timeout to be before setting
this. It would help if you can give us more info about the situation where this
happens, i.e. which connection is the problem. If you enable debug logging,
you'll hopefully get more information on when this happens.
--
Reply to this email directly or view it on GitHub:
https://github.com/osm2pgsql-dev/osm2pgsql/discussions/2290#discussioncomment-11818085
You are receiving this because you are subscribed to this thread.
Message ID:
<osm2pgsql-dev/osm2pgsql/repo-discussions/2290/comments/[email protected]>
_______________________________________________
Tile-serving mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/tile-serving
