Re: [GENERAL] Index pg_proc_prosrc_index: NUMBER OF INDEX' TUPLES (1071)ISNOT THE SAME AS HEAP' (1070)
| От | Bruce Momjian |
|---|---|
| Тема | Re: [GENERAL] Index pg_proc_prosrc_index: NUMBER OF INDEX' TUPLES (1071)ISNOT THE SAME AS HEAP' (1070) |
| Дата | |
| Msg-id | 199912220618.BAA00473@candle.pha.pa.us обсуждение исходный текст |
| Ответ на | Re: [GENERAL] Index pg_proc_prosrc_index: NUMBER OF INDEX' TUPLES (1071)ISNOT THE SAME AS HEAP' (1070) (Ed Loehr <ELOEHR@austin.rr.com>) |
| Список | pgsql-general |
> > I think it is harmless. To fix it properly requires a > > very sophisticated write-ahead log that is scheduled for 7.1 in about > > six months. > > This problem stops my psql dead in its tracks for related queries even across new > sessions. Requires a rebuild of indices before any queries work with the related > tables/functions, and since I don't know which one to rebuild (die, horsey, die), I > might as well rebuild them all. In production mode, that means stopping user access due > to the possibility of violating unique constraints enforced by unique indices. That > means downtime, which would makes moi persona non grata. But maybe my assumptions are > incorrect or I didn't understand what you mean by harmless? Maybe other people can chime in here. Why are you getting the inital crashes? -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
В списке pgsql-general по дате отправления: