hi all.
I'm here again.
as for the question I posed last time, which is titled "vacuuuuuuuuuuuuum!!!"
I found another thing.
it's only the first time when "vacuum" works.
after second time, memory isn't decreased any more.
when you re-startet POSTMASTER, "vacuum" decrease memory again.
also, when our system not working, it works completely fine.
on the logs, I found following NOTICEs;
NOTICE: InvalidateSharesInvalid: cache state reset
NOTICE: RegisterSharedInvalid: SI buffer overflow
though, I'm not sure if it has something todo with the problem I'm having now.
DBmemory seems to be enough, only 33% is used now.
my PostgreSQL version is 7.0.2, so no bugs seem to affect it.
please any help! thanks
----- following is the last question I posed -------
to PostgreSQL DB, I'm using "vacuum" command in a file which is executed at certain time
in a day by cron
the file is like follows;
psql inmsr <<EOF
delete from "TBL1" where "atime" < 'now';
commit;
delete from "TBL2" where "atime" < 'now'; commit;
delete from "TBL3" where "atime" < 'now';
commit;
vacuum analyze;
commit;
"delete" commands're done successfully, but when looking up the DB files
under /usr/local/pgsql/data/base/ ,
those tables still have some memories.
Also, keys that those tables have seem not to be deleted.
Does command "vacuum cannot clean up the keys ??
How can I "vacuum" up the memories??
OR, I might be wrong in a use of "vacuum" command.
could you tell me how it actually works?
what I want to do with this file is, to clean up the accumlated data from a DB
once in a month, so that we can save memory.
I do aprreciate for your advise. thank you!
hiroko Ogawa
