Re: BUG #5420: pg_attribute broken

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: BUG #5420: pg_attribute broken
Дата
Msg-id 201004150258.o3F2w0v10210@momjian.us
обсуждение исходный текст
Ответ на BUG #5420: pg_attribute broken  ("cool" <coolshower2008@yahoo.co.jp>)
Список pgsql-bugs
That is a serious problem.  Based on your ASAP requirement, I think you
need a commercial support contract or consultant to fix this for you.

---------------------------------------------------------------------------

cool wrote:
>
> The following bug has been logged online:
>
> Bug reference:      5420
> Logged by:          cool
> Email address:      coolshower2008@yahoo.co.jp
> PostgreSQL version: 8.1.8
> Operating system:   debian 2.6.18-6-686
> Description:        pg_attribute broken
> Details:
>
> We use PostgreSQL Databse on Hospital Information System in Japan.
> In case of normal condition(Not busy, Not Backup, Not Start up and Not
> Shutdown),
> Suddenly, PostgreSQL outputs error message  and "pg_attribute" catalog file
> is broken as bellow.
> Could you sent it to us A.S.A.P.
> <Environment>
>    debian debian 2.6.18-6-686 / PostgreSQL 8.1.8
> <Error message>
>    invalid attribute number 0 for tbl_syuday
> <pg_attribute>
>      attrelid     addname           atttypid    attstattarget   attlen
> attnum
>      45762        tableoid          26          0               4
> -7
>      45762        cmax              29          0               4
> -6
>      45762        xmax              28          0               4
> -5
>      45762        cmin              29          0               4
> -4
>      45762        xmin              28          0               4
> -3
>      45762        ctid              27          0               6
> -1
>      45762        santeiflg18_4      0          0               0
> 0 (?)
>      45762        nyugaikbn       1042         -1              -1
> 1
>      45762        ptid            1700         -1              -1
> 2
>      .
>      .(Omission)
>      .
>      45762        santeiflg17_1   1700         -1              -1
> 343
>      45762        ftmoney17_1     1700         -1              -1
> 344
>      45762        ftmoney18_4     1700         -1              -1
> 380 (345..379 are deleted?)
>      45762        comptfn18_4     1700         -1              -1
> 381
>      .
>      .(Omission)
>      .
> Q1:Does anything have same reports ?
> Q2:Does anything have repair patches ?
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

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

Предыдущее
От: Craig Ringer
Дата:
Сообщение: Re: Bug in CREATE FUNCTION with character type (CONFIRMED BUG)
Следующее
От: Tom Lane
Дата:
Сообщение: Re: BUG #5418: psql exits after using tab-completion with error message