| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com> |
| Cc: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Massive delete from a live production DB |
| Date: | 2011-05-12 16:04:56 |
| Message-ID: | BANLkTi=JOTrn2nOiyGZa_uG0Fos_-fSqxQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, May 12, 2011 at 8:23 AM, Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com> wrote:
> Hi
>
> Been reading some old threads (pre 9.x version) and it seems that the
> consensus is to avoid doing massive deletes from a table as it'll
> create so much unrecoverable space/gaps that vacuum full would be
> needed. Etc.
> Any ideas on what I could do without losing all the live updates? I
> need to get rid of about 11% of a 150 million rows of database, with
> each row being nearly 1 to 5 KB in size...
11% is not big deal as the space will get re-used for future updates
and inserts.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bob Pawley | 2011-05-12 16:32:00 | Postgredac Dump |
| Previous Message | Phoenix Kiula | 2011-05-12 15:37:11 | Re: Massive delete from a live production DB |