There are actually two issues sitting here:
1. Transaction Recovery and
2. Knowing when you've lost a connection and when to restart it.
I am not familiar with PostgreSQL but with a transaction oriented
database such as Firebird or Oracle, when you lose a connection,
re-connecting doesn't
On 12/11/17 09:30, Graeme Geldenhuys wrote:
On 2017-11-11 18:41, Mark Morgan Lloyd wrote:> the FPC/Lazarus controls
do a good job of presenting a common API> irrespective of what backend
server is being used, would it be feasible> to have a "reconnect
monitor" or similar to help recover from
On 2017-11-11 18:41, Mark Morgan Lloyd wrote:
the FPC/Lazarus controls do a good job of presenting a common API
irrespective of what backend server is being used, would it be feasible
to have a "reconnect monitor" or similar to help recover from this sort
of thing?
You should always program
Graeme started a short thread on databases in "The Other Place" a few
days ago, but I thought this might be of sufficient general relevance to
raise here.
I had a system outage this morning, with all apps suddenly losing their
connectivity to the PostgreSQL server.
It turned out that the
