Re: Serious Crash last Friday

doing pg_filedump -i FILENAME on the 16584 file I have all Block ids from 0
to 1150


select * from pg_class where oid = 16584
-> relname altseiten
-> reltoastidxid 0

yes, you are right 16584 is the oid of the table altseiten, but the
reltoastidxid is
still 0.


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@topconcepts.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: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Henrik Steffen" <steffen@city-map.de>
Cc: "pg" <pgsql-general@postgresql.org>
Sent: Thursday, July 11, 2002 8:36 AM
Subject: Re: [GENERAL] Serious Crash last Friday


> "Henrik Steffen" <steffen@city-map.de> writes:
> > I now did a "pg_filedump -R 1048595 16584" on the file
> > /var/lib/pgsql/data/base/16556/16584
>
> What file is that?  Doesn't look like it is an index ...
>
> > It delivered the following output. Can you read anything from it?
>
> Not a lot.  I'd suggest "pg_filedump -i FILENAME" where FILENAME is the
> OID of the toast-table index for your problem table.  (Look at
> pg_class.reltoastidxid if you're not sure.)  That should produce a ton
> of output along the lines of
>
>  Item 155 -- Length:   12  Offset: 4720 (0x1270)  Flags: USED
>   Block Id: 4  linp Index: 39  Size: 12
>   Has Nulls: 0   Has Varlenas: 0
>
> What you want to look for is outrageously large values in the "Block Id"
> field.  Once you find 'em, a "pg_filedump -i -f" of just the block
> containing the broken item(s) would be worth studying.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html