Adding basic retry-with-backoff to the /i/ endpoint will take pressure off Lightning instance administrators to maintaining high-availability in their Postgres deployments.

We don't reply to the webhook request until it's in the DB, but nothing's stopping us from trying again if we get a DBConnectionError and delaying that response by up to 60s.

Needs more detail from @stuartc