Re: Serious Crash last Friday
От | Henrik Steffen |
---|---|
Тема | Re: Serious Crash last Friday |
Дата | |
Msg-id | 044701c215e2$ac1143c0$7100a8c0@topconcepts.net обсуждение исходный текст |
Ответ на | Serious Crash last Friday ("Henrik Steffen" <steffen@city-map.de>) |
Ответы |
Re: Serious Crash last Friday
|
Список | pgsql-general |
same employee table (but after initdb, and restored from fridays dump) how can i find out the correct length of the tuples? 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: "Martijn van Oosterhout" <kleptog@svana.org> To: "Henrik Steffen" <steffen@city-map.de> Cc: <pgsql-general@postgresql.org> Sent: Monday, June 17, 2002 11:27 AM Subject: Re: [GENERAL] Serious Crash last Friday > On Mon, Jun 17, 2002 at 10:39:21AM +0200, Henrik Steffen wrote: > > > > Hello, > > > > trying pgfsck on my corrupted employee table from friday it gave me about 85 > > lines complaining > > about "Tuple incorrect length (parsed data=xxxxxx, length=xxx)" > > > > the table had 184 rows, out of which 85 were corrupt ?? > > Hmm, it depends mostly on whether the parsed was greater or less than the > length. If it's less than it is something to do with additional padding > being added at the end, which I havn't worked out yet. I'm thinking of > supressing the warning where the remaining looks like padding. > > If it's greater, there is a problem. > > > trying pgfsck on the current employee table of today (after new initdb etc.) > > with 184 rows, > > I get 814 (!!) rows complaining about "Tuple incorrect length ..." - how can > > this be??? > > Same or different tables? > -- > Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/ > > There are 10 kinds of people in the world, those that can do binary > > arithmetic and those that can't.
В списке pgsql-general по дате отправления: