Re: Serious Crash last Friday

ok -- now this is what I did now:

I tried to figure out, where exactly the problem was:

The error occured while trying to COPY table seiten to STDOUT

Now I did "SELECT * FROM seiten;" ---> same problem

table seiten looks as follows:

lfdseitenr char(9)
absatznr smallint
absatz text
bildtyp smallint
bildtext text
richt boolean

there are 22409 rows - and there is an index on lfdseitenr

using LIKE I tried to figure out which rows where affected

SELECT * FROM seiten WHERE lfdseitenr LIKE '08%';

finally I found out that it was only ONE single row,
lfdseitenr = 081400023 AND absatznr=3

SELECT lfdseitenr, absatznr, bildtyp, bildtext, richt FROM seiten WHERE
lfdseitenr = '081400023' AND absatznr=3;

so only ONE field in ONE particular row was destroyed (pg_toast - error
message -
no such file or directory)

I now created a temp table selecting EVERYTHING but the affected row and
renamed
the table. So the problem is solved now, but this should actually never
happen.

I have the temp-table left on my system. Is it possible that someone entered
invalid
characters or something into this particular text-fild "absatz" ? Or what
else could
cause this error? Maybe anyone of the postgres-'gurus' wants to have a look
on my
system? Maybe there is a bug anywhere in postgres? Doesn't look like a
hardware-problem
or what do you guys think?

Mit freundlichem Gruß

Henrik Steffen
Geschäftsführer

top concepts Internetmarketing GmbH
Am Steinkamp 7 - D-21684 Stade - Germany
--------------------------------------------------------
http://www.topconcepts.com Tel. +49 4141 991230
mail: steffen(at)topconcepts(dot)com Fax. +49 4141 991233
--------------------------------------------------------
24h-Support Hotline: +49 1908 34697 (EUR 1.86/Min,topc)
--------------------------------------------------------
System-Partner gesucht: http://www.franchise.city-map.de
--------------------------------------------------------
Handelsregister: AG Stade HRB 5811 - UstId: DE 213645563
--------------------------------------------------------

----- Original Message -----
From: "Henrik Steffen" <steffen(at)city-map(dot)de>
To: "Andrew Sullivan" <andrew(at)libertyrms(dot)info>
Cc: "pg" <pgsql-general(at)postgresql(dot)org>
Sent: Wednesday, July 10, 2002 5:19 PM
Subject: Re: [GENERAL] Serious Crash last Friday

> Hi,
>
> thanks for the information...
>
> the badblocks read-only test did not report any problems,
> do you think i should run the "read-write" test, too?
>
> i did the last initdb 3 weeks ago and created every table new from dumps.
> i am recreating all user-indexes every day, i am vacuuming everything
> everyday.
>
> the server has only been running for 4 months, it's brand new hardware
> (Intel PIII,
> 900 MHz, 2 x 60 GB SCSI-Raid 0 disks) ... it has been up and running for
42
> days
> without reset now (last reset was due to work at powerswitch).
>
> tonight I will have the memory checked by memtest86 ...
>
>
> Mit freundlichem Gruß
>
> Henrik Steffen
> Geschäftsführer
>
> top concepts Internetmarketing GmbH
> Am Steinkamp 7 - D-21684 Stade - Germany
> --------------------------------------------------------
> http://www.topconcepts.com Tel. +49 4141 991230
> mail: steffen(at)topconcepts(dot)com Fax. +49 4141 991233
> --------------------------------------------------------
> 24h-Support Hotline: +49 1908 34697 (EUR 1.86/Min,topc)
> --------------------------------------------------------
> System-Partner gesucht: http://www.franchise.city-map.de
> --------------------------------------------------------
> Handelsregister: AG Stade HRB 5811 - UstId: DE 213645563
> --------------------------------------------------------
>
> ----- Original Message -----
> From: "Andrew Sullivan" <andrew(at)libertyrms(dot)info>
> To: "pg" <pgsql-general(at)postgresql(dot)org>
> Sent: Wednesday, July 10, 2002 4:38 PM
> Subject: Re: [GENERAL] Serious Crash last Friday
>
>
> > On Wed, Jul 10, 2002 at 02:51:00PM +0200, Henrik Steffen wrote:
> > > excuse me, but what is a "non-destructive badblocks (or
> > > whatever) test" - and how can I do this?
> >
> > If you're using linux, try "man badblocks".
> >
> > On Solaris, a similar command is diskscan.
> >
> > Other systems will have other names. I can't recall how to do this
> > on BSD, and I can't find anything in my local man db at the moment.
> > I'll bet someone else here knows.
> >
> > You should check for other hardware faults, too. A bad memory module
> > can provide for all sorts of strange errors on your system (although
> > if it never locks up or crashes, I'd look elsewhere for the problem
> > first). In recent releases, PostgreSQL has proven to be very stable,
> > but you are having a lot of trouble, and many others are not
> > reporting similar problems. That leads one to suspect that you have
> > faulty hardware; it certainly requires, at least, that you eliminate
> > hardware as a factor.
> >
> > A
> >
> > --
> > ----
> > Andrew Sullivan 87 Mowat Avenue
> > Liberty RMS Toronto, Ontario Canada
> > <andrew(at)libertyrms(dot)info> M6K 3E3
> > +1 416 646 3304 x110
> >
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 3: if posting/reading through Usenet, please send an appropriate
> > subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> > message can get through to the mailing list cleanly
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org