From: | Matthew <matt(at)ctlno(dot)com> |
---|---|
To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Matthew <matt(at)ctlno(dot)com> |
Cc: | "'Mikheev, Vadim'" <vmikheev(at)SECTORBASE(dot)COM>, pgsql-hackers(at)postgresql(dot)org |
Subject: | RE: 7.0.3 _bt_restscan: my bits moved right off the end of the world! |
Date: | 2001-03-23 18:51:43 |
Message-ID: | 183FA749499ED311B6550000F87E206C1FD09B@srv.ctlno.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Matthew <matt(at)ctlno(dot)com> writes:
> > FYI now when I try to use psql to connect to the database I get this
> > error:
> > bash$ psql cms
> > psql: FATAL 1: cannot find attribute 1 of relation pg_trigger
>
> So the indexes on pg_attribute are hosed too. I wonder whether that was
> the original source of the problem, and the rest of this is
> side-effects?
>
> I am starting to think that you'd best initdb and reload, but there is
> one more thing to try: run REINDEX on the whole database in standalone
> mode. See the documentation for the procedure; I'm not too clear on it
> since I've never had to do it myself.
>
> regards, tom lane
>
What do you mean by the whole database? I have already executed:
reindex database cms force
reindex table cases force
reindex table cases force
reindex table hits force
reindex table history force (and a few more)
How do I get it do reindex the system tables? One table at a time?
From | Date | Subject | |
---|---|---|---|
Next Message | Mikheev, Vadim | 2001-03-23 18:57:59 | RE: 7.0.3 _bt_restscan: my bits moved right off the end of the world! |
Previous Message | Tom Lane | 2001-03-23 18:51:35 | Re: 7.0.3 _bt_restscan: my bits moved right off the end of the world! |