| From: | Francisco Reyes <lists(at)natserv(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Ken Corey <ken(dot)corey(at)atomic-interactive(dot)com>, <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: Disk space problem... |
| Date: | 2001-12-08 14:11:29 |
| Message-ID: | 20011208090932.I29902-100000@zoraida.natserv.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
On Sat, 1 Dec 2001, Tom Lane wrote:
> Ken Corey <ken(dot)corey(at)atomic-interactive(dot)com> writes:
> > Several of my tables are being emptied and totally replaced (statistics about
> > how my website is running, that sort of thing). Is it better to drop the
> > table, and rebuild it in this case?
>
> Consider TRUNCATE.
Does truncate releases all the space from the indexes?
> I suspect if you look at the stats (see pg_class.relpages) you'll find
> that the space VACUUM fails to reclaim is in indexes.
Does it mean that if records are deleted an one does vacuum, that index
space may not be released?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aarni Ruuhimäki / Megative Tmi / KYMI.com | 2001-12-09 18:29:18 | Fwd: Backup automation |
| Previous Message | Andrew McMillan | 2001-12-08 03:27:40 | Re: IF...THEN...ELSE on INSERT |