Message-Id: <3.0.1.32.19990420121339.009b4140@ori-ind.com>
Date: Tue, 20 Apr 1999 12:13:39 -0700
To: JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
From: "Ken J. Wright" <ken@ori-ind.com>
Subject: Re: [INTERFACES] TUPLES <> HEAP
Cc: pgsql-interfaces@postgreSQL.org
In-Reply-To: <01BE8B3E.4C03C020.jt-kirkpatrick@mpsllc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

You might just dump the database, drop it, & re-create it.

pg_dump -f outfile
destroydb dbname
psql -f outfile

Ken

At 02:58 PM 04/20/1999 -0400, you wrote:
>Hi all.  Head hanging a little low, even though system still seems to work 
>fine.  Here is what I did:
>
>- update pg_class set relname = lower(relname);
>- update pg_attribute set attname = lower(attname);
>- (why did I do that?  Following something I read, not really having 
>problems in the first place and  not really knowing the effects).
>
>Now when I vacuum I get the error messages:
>NOTICE:  Index pg_class_relname_index: NUMBER OF INDEX' TUPLES (108) IS NOT 
>THE SAME AS HEAP' (82)
>NOTICE:  Index pg_class_oid_index: NUMBER OF INDEX' TUPLES (108) IS NOT THE 
>SAME AS HEAP' (82)
>
>I'd like to drop these indexes and re-create them, hoping that would solve 
>the problem.  But I tried to drop them and postgres wouldn't let me - 
>claiming they were system catalog indexes.  Would dropping and recreating 
>the indexes get rid of the error messages?  If so, how can I drop them and 
>what is the proper way to recreate them?
>
>Newbie mistakes aren't much fun.  Thanks for helping. . .
>
>jt
>
>