gt; Cc : 'PostgreSQL Hackers Mailing List'
> Objet : Re: [HACKERS] Stability problems
>
> I would recommend checking your memory (look for memtest86 online
> somewhere. Good tool.) Anytime a machine seems to act flakely
there's a
> better than even chance it has a
> > Scott you're right, it was a hardware problem.
> > Thanks for your help.
> >
>
> Glad to be of help. What was the problem? Bad memory or bad hard
drive?
> Just curious.
It was a bad 512Mo memory module and a bad memory slot on the
motherboard.
Our hosting provider never checks memory before
On Tue, 12 Nov 2002, Nicolas VERGER wrote:
> Scott you're right, it was a hardware problem.
> Thanks for your help.
>
Glad to be of help. What was the problem? Bad memory or bad hard drive?
Just curious.
---(end of broadcast)---
TIP 6: Have y
VERGER
> Cc : 'PostgreSQL Hackers Mailing List'
> Objet : Re: [HACKERS] Stability problems
>
> I would recommend checking your memory (look for memtest86 online
> somewhere. Good tool.) Anytime a machine seems to act flakely
there's a
> better than even chance
I would recommend checking your memory (look for memtest86 online
somewhere. Good tool.) Anytime a machine seems to act flakely there's a
better than even chance it has a bad bit of memory in it.
On Wed, 6 Nov 2002, Nicolas VERGER wrote:
> Hi,
> I have strange stability problems.
> I can't ac
"Nicolas VERGER" <[EMAIL PROTECTED]> writes:
> 2002-11-05 14:46:44 [5768] FATAL 2: failed to add item with len = 191
> to page 150 (free space 4294967096, nusd 0, noff 0)
> template1=# select version();
> PostgreSQL 7.2.1 on i686-pc-linux-gnu, compiled by GCC 2.96
Hmm. This looks a lot like t