From: | Jord Tanner <jord(at)indygecko(dot)com> |
---|---|
To: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: kill -2 |
Date: | 2004-04-21 21:43:58 |
Message-ID: | 1082583838.17997.298.camel@gecko |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)indygecko(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | Dann Corbit | 2004-04-21 21:55:51 | Re: 7.3.4 on Linux: UPDATE .. foo=foo+1 degrades massivly over time |
Previous Message | Froggy / Froggy Corp. | 2004-04-21 20:56:33 | Re: PL/SQL question |