From: | Andrew Sullivan <andrew(at)libertyrms(dot)info> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Please help with this error message |
Date: | 2003-03-26 22:04:50 |
Message-ID: | 20030326170450.D5705@mail.libertyrms.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Mar 26, 2003 at 10:19:24AM -0700, Chris Smith wrote:
> Okay, after looking through several pages of those search results and
> finding nothing that resembles a link to a disk or memory test, I gave up.
What hardware are you using? If you're using x86 hardware,
memtestx86 is your best bet. Linux has badblocks for disk checking;
other systems do this in other ways (with VxFS, you get notified
automatically by Solaris, for instance).
> Again, since this happens on multiple servers, it's unlikely to be a
> hardware problem in the first place. Anyone have other ideas?
I don't think that's true. If you got bad data in the first time,
you'll probably have it in all the systems. SELECT might turn it up
when COPY wouldn't, because AFAIK COPY just spits out what it finds.
A
--
----
Andrew Sullivan 204-4141 Yonge Street
Liberty RMS Toronto, Ontario Canada
<andrew(at)libertyrms(dot)info> M2P 2A8
+1 416 646 3304 x110
From | Date | Subject | |
---|---|---|---|
Next Message | Gary Hendricks | 2003-03-26 22:30:07 | Any recommendations for books on PostgreSQL? |
Previous Message | Chris Smith | 2003-03-26 21:20:46 | Re: Please help with this error message |