Date: Wed, 13 Mar 2013 18:26:12 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Gabriel =?iso-8859-1?Q?E=2E_S=E1nchez_Mart=EDnez?=
	<gabrielesanchez@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: tables mysteriously truncated
Message-ID: <20130313212612.GC3697@alvh.no-ip.org>
References: <5140B917.5060405@gmail.com>
	<CAF8jcqo+eqEuBrqp6=QhFrTDhg17He9hqiCMOhaMh9TfoYO5_w@mail.gmail.com>
	<5140C268.9080802@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <5140C268.9080802@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

"Gabriel E. S=E1nchez Mart=EDnez" escribi=F3:
> I will try to make these tables logged and see if they withstand the
> test of time.  Are crashes and unclean shutdowns logged anywhere?  I
> would like to see why I might be getting them.  I have not had to
> manually restart the database, if that were an indication of a
> crash.

Yes, crashes are logged in the server log.  There's support for
automatic recovery and restart after a crash, so it's quite plausible
that you're not seeing anything if you're not paying attention.
Sessions that were running prior to the crash are terminated, though, so
if you keep connections open, you'd notice because they would no longer
work.

Crashes should certainly not happen routinely.  If they are, you have a
problem that's worth investigating.

--=20
=C1lvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services


--=20
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin