pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedTUPLES <> HEAP
3+ messages / 3 participants
[nested] [flat]
* TUPLES <> HEAP
@ 1999-04-20 18:58 JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
0 siblings, 2 replies; 3+ messages in thread
From: JT Kirkpatrick @ 1999-04-20 18:58 UTC (permalink / raw)
To: 'pgsql-sql@hub.org' <pgsql-sql@hub.org>; 'pgsql-interfaces@hub.org' <pgsql-interfaces@hub.org>; 'pgsql-general@hub.org' <pgsql-general@hub.org>; 'pgsql-admin@hub.org' <pgsql-admin@hub.org>; 'pgsql-hackers@hub.org' <pgsql-hackers@hub.org>
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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: [GENERAL] TUPLES <> HEAP
@ 1999-04-20 19:08 Karl DeBisschop <kdebisschop@spaceheater.infoplease.com>
parent: JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
1 sibling, 0 replies; 3+ messages in thread
From: Karl DeBisschop @ 1999-04-20 19:08 UTC (permalink / raw)
To: jt-kirkpatrick@mpsllc.com; +Cc: pgsql-general@hub.org
Not sure that you can drop/create system indexes (I didn't notice that
when I posted earlier - sorry). But the the same idea may apply - can
you dump and recreate the database tables.
$ pg_dump existing > existing.dump
$ psql -e secondtry < exidting.dump
BTW, do you need to cross-post to all those lists? I'm sure hackers
is not needed, and you could probably drop interfaces and maybe some
others as well.
Hope this helps.
Karl
From: JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: [INTERFACES] TUPLES <> HEAP
@ 1999-04-20 19:13 Ken J. Wright <ken@ori-ind.com>
parent: JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
1 sibling, 0 replies; 3+ messages in thread
From: Ken J. Wright @ 1999-04-20 19:13 UTC (permalink / raw)
To: JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>; +Cc: pgsql-interfaces
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
>
>
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~1999-04-20 19:13 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-04-20 18:58 TUPLES <> HEAP JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
1999-04-20 19:08 ` Karl DeBisschop <kdebisschop@spaceheater.infoplease.com>
1999-04-20 19:13 ` Ken J. Wright <ken@ori-ind.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox