| From: | Shaun Thomas <sthomas(at)peak6(dot)com> |
|---|---|
| To: | Greg Spiegelberg <gspiegelberg(at)gmail(dot)com> |
| Cc: | "Reuven M(dot) Lerner" <reuven(at)lerner(dot)co(dot)il>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Marcin Mańk <marcin(dot)mank(at)gmail(dot)com>, <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Very long deletion time on a 200 GB database |
| Date: | 2012-02-23 18:05:01 |
| Message-ID: | 4F467FCD.8090100@peak6.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 02/23/2012 11:56 AM, Greg Spiegelberg wrote:
> I know there are perils in using ctid but with the LOCK it should be
> safe. This transaction took perhaps 30 minutes and removed 100k rows
> and once the table was VACUUM'd afterward it freed up close to 20 GB
> on the file system.
It took *30 minutes* to delete 100k rows? And 100k rows were using 20GB?
Is that off by an order of magnitude?
Using the ctid is a cute trick, though. :)
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-444-8534
sthomas(at)peak6(dot)com
______________________________________________
See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Colson | 2012-02-23 18:11:12 | Re: Very long deletion time on a 200 GB database |
| Previous Message | Steve Crawford | 2012-02-23 18:01:03 | Re: set autovacuum=off |