psql casts aspersions on server reliability

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: psql casts aspersions on server reliability
Date: 2016-09-28 12:22:11
Message-ID: CA+TgmoZYvqmyQpzSUdtDmtk4Aj94MppDGe9qVJczbPLy4G2Yfg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

psql tends to do things like this:

rhaas=# select * from pg_stat_activity;
FATAL: terminating connection due to administrator command
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.

Basically everything psql has to say about this is a lie:

1. It says the server closed the connection unexpectedly, but it just
finished processing a FATAL message from the server. So how
unexpected is it that the connection would thereafter be closed?

2. It says the server probably terminated abnormally, but PostgreSQL
is rarely so unreliable as to just give up the ghost and die. The
ErrorResponse it just processed has an errcode of
ERRCODE_ADMIN_SHUTDOWN, so probably what happened is somebody either
shut down the server or killed the session.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-09-28 12:35:15 Re: Tracking wait event for latches
Previous Message Michael Paquier 2016-09-28 11:55:49 Re: Password identifiers, protocol aging and SCRAM protocol