Re: Robert Haas > I wonder if, in addition to removing the hint, we could also consider > rewording the message. For example, a slight rewording to "server > connection closed unexpectedly" would avoid implying that it was the
There is a lot of software doing string-parsing of this part of the message, so it might be advisable to leave the first line alone. https://sources.debian.org/src/php-laravel-framework/10.48.25+dfsg-2/src/Illuminate/Database/DetectsLostConnections.php/?hl=28#L28 https://sources.debian.org/src/python-taskflow/5.9.1-4/taskflow/persistence/backends/impl_sqlalchemy.py/?hl=87#L87 https://sources.debian.org/src/gnucash/1:5.10-0.1/libgnucash/backend/dbi/gnc-backend-dbi.cpp/?hl=798#L798 https://sources.debian.org/src/pgbouncer/1.24.0-3/test/test_misc.py/?hl=301#L301 https://sources.debian.org/src/icingaweb2-module-reporting/1.0.2-2/library/Reporting/RetryConnection.php/?hl=23#L23 https://sources.debian.org/src/storm/1.0-1/storm/databases/postgres.py/?hl=353#L353 https://sources.debian.org/src/timescaledb/2.19.0+dfsg-1/test/expected/loader-tsl.out/?hl=473#L473 https://sources.debian.org/src/odoo/18.0.0+dfsg-2/addons/web/tests/test_db_manager.py/?hl=277#L277 https://codesearch.debian.net/search?q=server+closed+the+connection+unexpectedly&literal=1 (There might be room for asking why this string parsing is being done, is libpq missing "connection lost" detection vs. other errors?) The remaining message lines are admittedly very pessimistic about PostgreSQL's stability and should mention networking issues first. Christoph
