Thank you Tom! This query finds the culprit right away. There is one table that acts as a log file, storing the transactions sql that's happening on the db, so the db size grows when the logging is turned on. After doing some cleaning on this table, it shrinks the database to 500Mb again.Okay, so you have a lot of wide (toasted) fields in whatever table that toast table belongs to --- if you're not sure, try
select relname from pg_class where reltoastrelid = (select oid from pg_class where relfilenode = 25677563);
VACUUM VERBOSE on that table would give some useful info.
regards, tom lane
Just curious though, why the toast file for this transaction table takes the most space (the transaction table itself was only about 10Mb), considering there are a few other tables with bigger size (40Mb) than this transaction table but do not have toast file that's comparable in size to this one.
- reynard
---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
