From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_group_name_index corrupt? |
Date: | 2000-05-04 11:32:26 |
Message-ID: | Pine.BSF.4.21.0005040830140.92638-100000@thelab.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 4 May 2000, Tom Lane wrote:
> The Hermit Hacker <scrappy(at)hub(dot)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(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
From | Date | Subject | |
---|---|---|---|
Next Message | Don Baccus | 2000-05-04 12:45:07 | Re: system usage stats (Was: Re: Why Not MySQL? ) |
Previous Message | Vince Vielhaber | 2000-05-04 09:27:59 | Re: AW: Crack Warez Links,,Anonymous Posting Kit,,New--Anon ymousMAIL BOMB |