I have exactly the same problem.
For me, it's due to the fact that I create temporary tables within stored
procedures.
There is no easy alternative to correct this...
One way is to launch Postgres with -O -P options and then REINDEX DATABASE
xxx FORCE.
There is some discussion about this last days...
Look at discussion : 'pg_attribute always grow...'
Patrick Fiche
-----Original Message-----
From: pgsql-general-owner@postgresql.org
[mailto:pgsql-general-owner@postgresql.org]On Behalf Of
darthxiong@libero.it
Sent: Tuesday, October 22, 2002 11:49 AM
To: pgsql-general@postgresql.org
Subject: [GENERAL] big pg_attribute_relid_attnam_index files
hi all... i was peeking in the files of postgres ( 7.2.1 ) and found a 700Mb
file . looking in the system tables, i found that it corresponds to the
index
pg_attribute_relid_attnam_index. Also, pg_attribute_relid_attnum_index file
is similar. I set up another db usinc rsync, dumped the db, droppped it, and
restored. now the 2 files look normal.
I run vacuum --analize about 3 times a day. why that files become so big?
there is a solution, other than dump & restore ?
TIA
Ivan
--
Lucy: Dance, dance, dance. That is all you ever do.
Can't you be serious for once?
Snoopy: She is right! I think I had better think
of the more important things in life!
(pause)
Tomorrow!!
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
