Re: kill -2 - Mailing list pgsql-general

From Jord Tanner
Subject Re: kill -2
Date
Msg-id 1082583838.17997.298.camel@gecko
Whole thread Raw
In response to Re: kill -2  ("scott.marlowe" <scott.marlowe@ihs.com>)
Responses Re: kill -2
List pgsql-general
We are exploring the possibility of hardware problems, and have found
some issues with the LSILogic Megaraid driver running in 64bit (this is
a dual Opteron running Gentoo AMD64).

Thanks for the feedback. I'm just covering all the bases.

Jord Tanner

On Wed, 2004-04-21 at 12:59, scott.marlowe wrote:
> On Wed, 21 Apr 2004, Jord Tanner wrote:
>
> >
> > Greetings,
> >
> > Does anyone know what the effect of sending an INT signal (kill -2) to
> > each of:
> >         - pg backend
> >         - psql running an insert or select into
> >         - Perl script with DBI connection to pg, running insert or
> >         select into
> >         - vacuumdb
> >
> > I'm getting some database corruption, and I'm wondering if the use of
> > 'kill -2' could be the cause.
>
> No, kill -2 should not cause corruption.
>
> About once a month we get someone on the lists getting corruption.  almost
> every time it's either a bad hard drive, memory, or system/cpu/mobo
> causing it.  Have you tested your memory (memtest86) or drives (badblocks
> on linux) to make sure they aren't the cause of your problem?  Just
> because a server is new doesn't mean it's free of all flaws.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
--
Jord Tanner <jord@indygecko.com>


pgsql-general by date:

Previous
From: "Froggy / Froggy Corp."
Date:
Subject: Re: PL/SQL question
Next
From: majordomo-owner+T1B09-320B-997D@postgresql.org
Date:
Subject: Majordomo Delivery Error