| From: | James Cradock <jcradock(at)me3(dot)com> |
|---|---|
| To: | Douglas McNaught <doug(at)mcnaught(dot)org> |
| Cc: | Gábor Farkas <gabor(at)nekomancer(dot)net>, Alban Hertroys <alban(at)magproductions(dot)nl>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: to drop a 30GB database. is it slow? |
| Date: | 2005-09-30 12:44:19 |
| Message-ID: | 2c6a8188bcc42e25d33fd4430df0e78a@me3.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sep 30, 2005, at 8:21 AM, Douglas McNaught wrote:
>> so, what if simply dropping the table does not recover the disk-space?
>
> It will. Each table is stored in its own set of disk files, and when
> the table is dropped those files are simply deleted.
This is normally true. Vacuuming the database the table (or index) was
dropped from may free up disk space too.
Jim
-----
James Cradock, jcradock(at)me3(dot)com
me3 Technology Consultants, LLC
24 Preble Street, 2nd Floor
Portland, ME 04101
207-772-3217 (office)
207-838-8678 (mobile)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2005-09-30 13:23:29 | Re: Improving GROUP BY? |
| Previous Message | Douglas McNaught | 2005-09-30 12:21:25 | Re: to drop a 30GB database. is it slow? |