Re: pg_clog woes with 7.3.2 - Episode 2

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_clog woes with 7.3.2 - Episode 2
Date: 2003-04-17 07:27:48
Message-ID: 03AF4E498C591348A42FC93DEA9661B83AF045@mail.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: 16 April 2003 16:22
> To: Dave Page
> Cc: pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] pg_clog woes with 7.3.2 - Episode 2
>
>
> How annoying. My bet would be on the SCSI adaptor being the
> problem. Or you could have a cabling issue --- SCSI is not as
> bad as IDE, but it's still finicky, esp w.r.t. termination.

OK, I've now tried a 29160N adaptor with a DPT cable (with non-removable
terminator as per the previous Adaptec cable), and have even removed the
DAT drive from the system and I still see the same sort of errors
following an initdb/reload.

A couple of things I've noticed:

- It always crashes on the same database which is some way through the
original dump file and my vacuum script. If I drop that one it may or
may not crash on another one further through the script.

- Sometimes everything works fine until I reboot the system.

I'll see if I can downgrade the kernel later today though it's all a bit
hectic with the easter break tomorrow so it may have to wait until next
week.

Still, if anyone has any more ideas, I'd be grateful...

Regards, Dave.

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Page 2003-04-17 07:32:40 Re: pg_clog woes with 7.3.2 - Episode 2
Previous Message Oliver Elphick 2003-04-17 06:54:36 New flex