Re: [GENERAL] More details on Database corruption

From: "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: George Kousi <g(dot)kousi(at)albourne(dot)com>, PostgreSQL-development <hackers(at)postgreSQL(dot)org>
Subject: Re: [GENERAL] More details on Database corruption
Date: 1998-08-24 15:01:39
Message-ID: 35E18053.EAADE501@alumni.caltech.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

> The problem is that the DEFAULT string is
> not the same length as the column. Anyone know how to fix this?

I can put this on my list of things to look at, but I'm not sure why
this is causing the backend to crash. Is is a problem with storage
allocation when updating columns? Or is it a problem with storage which
is already corrupted by the zero-length default character strings?? I
would think that the default string is not looked at during the update,
so the damage happened during the initial insert, right?

- Tom

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 1998-08-24 15:38:03 Re: [GENERAL] More details on Database corruption
Previous Message Sferacarta Software 1998-08-24 07:54:23 Re[2]: [GENERAL] DELETE statement KILL backend <AGAIN>

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas G. Lockhart 1998-08-24 15:27:59 Re: [HACKERS] Open 6.4 items
Previous Message Eric Marsden 1998-08-24 14:54:46 Re: [INTERFACES] Convert PGconn, PGresult to opaque types?