Re: Safely Killing Backends - Mailing list pgsql-general

From Vivek Khera
Subject Re: Safely Killing Backends
Date
Msg-id x7is52vkff.fsf@yertle.int.kciLink.com
Whole thread Raw
In response to Applications that leak connections  (Paul Tillotson <pntil@shentel.net>)
Responses Re: Safely Killing Backends
List pgsql-general
>>>>> "TFO" == Thomas F O'Connell <Thomas> writes:

TFO> Which brings up a follow-up question: is it documented anywhere
TFO> exactly what goes on in recovery mode? If so, I've not found it.

TFO> When I've experienced this, it has seemed quicker just to stop and
TFO> restart postgres than to let recovery mode complete. Is that unsafe?

The recovery has to happen at some point.  What it is doing is
bringing your DB to a known valid state based on the committed
transactions, what's written to disk, and what's written to the
pg_xlog files.  A vacuum is probably in good order after this happens.

Effectively, it does the moral equivalent of unplugging the power cord
and restarting itself, without the bother of needing to reboot the
whole machine :-)

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D.                Khera Communications, Inc.
Internet: khera@kciLink.com       Rockville, MD  +1-301-869-4449 x806
AIM: vivekkhera Y!: vivek_khera   http://www.khera.org/~vivek/

pgsql-general by date:

Previous
From: "NTPT"
Date:
Subject: More concurent transaction over single connection ?
Next
From: javier wilson
Date:
Subject: Re: Database permissions