Re: [GENERAL] More details on Database corruption - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [GENERAL] More details on Database corruption
Date
Msg-id 199808241538.LAA01205@candle.pha.pa.us
Whole thread Raw
In response to Re: [GENERAL] More details on Database corruption  ("Thomas G. Lockhart" <lockhart@alumni.caltech.edu>)
List 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?

It is an Assert which is saying, 'If it is a fixed-length field, it
better have the same length.'

Do you want the backtrace line?

--
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
  +  If your life is a hard drive,     |  (610) 353-9879(w)
  +  Christ can be your backup.        |  (610) 853-3000(h)

pgsql-hackers by date:

Previous
From: "Thomas G. Lockhart"
Date:
Subject: Re: [HACKERS] Open 6.4 items
Next
From: Bruce Momjian
Date:
Subject: Re: [INTERFACES] Re: [HACKERS] Convert PGconn, PGresult to opaque types?