| From: | Bill Thoen <bthoen(at)gisnet(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | When to use Vacuum? |
| Date: | 2010-06-24 17:16:45 |
| Message-ID: | 4C2392FD.3000306@gisnet.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I'm putting some large read-only data sets together and occasionally I
change my mind about something, drop a table or two and replace them
with something different. Do I need to use VACUUM when I drop or
re-arrange tables? Or does PG release disk space when you drop tables?
And finally, if the tables are strictly read-only, then do I need to
use VACUUM at all on a regular basis? (Like, do selections take up disk
space that needs to be cleaned up on a regular basis? It's my
understanding that VACUUM only clears or marks for re-use deleted
records, but the docs say nothing about deleted tables and I don't want
to get into an intolerable situation someday (like disk full.)
TIA,
- Bill Thoen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anders Steinlein | 2010-06-24 17:18:22 | Filtering by tags |
| Previous Message | Sim Zacks | 2010-06-24 16:31:55 | Re: complicated running aggregate |