Re: pg_group_name_index corrupt?

Поиск
Список
Период
Сортировка
От The Hermit Hacker
Тема Re: pg_group_name_index corrupt?
Дата
Msg-id Pine.BSF.4.21.0005040830140.92638-100000@thelab.hub.org
обсуждение исходный текст
Ответ на Re: pg_group_name_index corrupt?  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: pg_group_name_index corrupt?  (Tom Lane <tgl@sss.pgh.pa.us>)
RE: pg_group_name_index corrupt?  ("Hiroshi Inoue" <Inoue@tpf.co.jp>)
Список pgsql-hackers
On Thu, 4 May 2000, Tom Lane wrote:

> The Hermit Hacker <scrappy@hub.org> writes:
> > This worry anyone? :)
> > NOTICE:  Index pg_group_sysid_index: NUMBER OF INDEX' TUPLES (0) IS NOT THE SAME AS HEAP' (1).
> >         Recreate the index.
> > NOTICE:  Index pg_group_name_index: NUMBER OF INDEX' TUPLES (0) IS NOT THE SAME AS HEAP' (1).
> >         Recreate the index.
> 
> Not if you had other transactions running in parallel with the
> vacuum --- if the vacuum was the only thing running then I'd want
> to know what you were doing before that...

I can't guarantee whether i was or not :(  right now, I'm assuming that
'other transactions' would include any database on that server, not just
the database that I was vacuuming at the time, as even if I go in and do a
vacuum on 'template1', that error pops up ...

It says to 'recreate the index', but if I try to, it tells me its a system
table (of course) ... is there a way of fixing this without having to do
a dump/reload?


Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 



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

Предыдущее
От: Vince Vielhaber
Дата:
Сообщение: Re: AW: Crack Warez Links,,Anonymous Posting Kit,,New--Anon ymousMAIL BOMB
Следующее
От: Don Baccus
Дата:
Сообщение: Re: system usage stats (Was: Re: Why Not MySQL? )