From: | Mark Morgan Lloyd <markMLl(dot)pgsql-general(at)telemetry(dot)co(dot)uk> |
---|---|
To: | pgsql-general(at)PostgreSQL(dot)org |
Subject: | pg on Debian servers |
Date: | 2017-11-11 13:03:18 |
Message-ID: | ou6sem$qrd$1@pye-srv-01.telemetry.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Apologies for something which is distro related, but I was bitten by a
"silly mistake"- one of my own, I hasten to say- earlier.
Several legacy programs written in Delphi ground to a halt this morning,
which turned out to be because a Debian system had updated its copy of
PostgreSQL and restarted the server, which broke any live connections.
At least some versions of Delphi, not to mention other IDE/RAD tools
with database-aware components, don't automatically try to reestablish a
database session that's been interrupted. In any event, an unexpected
server restart (irrespective of all investment in UPSes etc.) has the
potential of playing havoc on a clustered system.
Is there any way that either the package maintainer or a site
administrator/programmer such as myself can mark the Postgres server
packages as "manual upgrade only" or similar? Or since I'm almost
certainly not the first person to be bitten by this, is there a
preferred hack in mitigation?
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2017-11-11 13:21:16 | Re: pg on Debian servers |
Previous Message | Lele Gaifax | 2017-11-11 11:29:37 | Difference between CAST(v AS t) and v::t |