On some managed databases, the timeout for idle transactions is relatively low
(for the scope of the work that `osm2pgsql` does). On Neon, for example, the
timeout value for idle transactions is 5 minutes.
When we are processing a large file, it's very easy for this timeout to
trigger. On Neon this will lead to something like
```sh
[CRITICAL]: Exception during execution: SSL connection has been closed
unexpectedly
```
To workaround this, we can change the timeout value for the role used by
`osm2pgsql`
```SQL
ALTER ROLE role_name SET idle_in_transaction_session_timeout='1200s';
```
However, I think it would be nice if this was done automatically by `osm2pgsql`
at the session level.
--
Reply to this email directly or view it on GitHub:
https://github.com/osm2pgsql-dev/osm2pgsql/discussions/2290
You are receiving this because you are subscribed to this thread.
Message ID: <osm2pgsql-dev/osm2pgsql/repo-discussions/[email protected]>
_______________________________________________
Tile-serving mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/tile-serving
