Re: [GENERAL] More details on Database corruption

Поиск
Список
Период
Сортировка
От Thomas G. Lockhart
Тема Re: [GENERAL] More details on Database corruption
Дата
Msg-id 35E18053.EAADE501@alumni.caltech.edu
обсуждение исходный текст
Ответ на Re: [GENERAL] More details on Database corruption  (Bruce Momjian <maillist@candle.pha.pa.us>)
Ответы Re: [GENERAL] More details on Database corruption
Список 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

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: [HACKERS] minor problem with detecting int64 in configure
Следующее
От: Eric Marsden
Дата:
Сообщение: Re: [INTERFACES] Convert PGconn, PGresult to opaque types?