public inbox for [email protected]
help / color / mirror / Atom feedFrom: Christoph Berg <[email protected]>
To: Robert Haas <[email protected]>
Cc: Andres Freund <[email protected]>
Cc: [email protected]
Subject: Re: libpq maligning postgres stability
Date: Thu, 27 Mar 2025 17:03:11 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+Tgmoau2bCgX+5uzKvTzHyzeXe28Sr-Kwe+LPAxTsFGdpjzkw@mail.gmail.com>
References: <up7whuxn263agr7whdzzoak7mo7ywryc7z7z3ejdvgbbke4vji@3puckkgm4ide>
<CA+Tgmoau2bCgX+5uzKvTzHyzeXe28Sr-Kwe+LPAxTsFGdpjzkw@mail.gmail.com>
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/Detects...
https://sources.debian.org/src/python-taskflow/5.9.1-4/taskflow/persistence/backends/impl_sqlalchemy...
https://sources.debian.org/src/gnucash/1:5.10-0.1/libgnucash/backend/dbi/gnc-backend-dbi.cpp/?hl=798...
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...
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
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: libpq maligning postgres stability
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox