Re: Massive delete of rows, how to proceed?

From: andrew(at)pillette(dot)com
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Massive delete of rows, how to proceed?
Date: 2006-11-26 00:35:01
Message-ID: 200611260035.kAQ0Z1G02487@pillette.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

I don't believe DROP is necessary; use TRUNCATE instead. No need to re-create dependent objects.

"Peter Childs" <peterachilds(at)gmail(dot)com> wrote ..
> On 24/11/06, Arnau <arnaulist(at)andromeiberica(dot)com> wrote:
> > Hi all,
> >
> > I have a table with statistics with more than 15 million rows. I'd
> > like to delete the oldest statistics and this can be about 7 million
> > rows. Which method would you recommend me to do this? I'd be also
> > interested in calculate some kind of statistics about these deleted
> > rows, like how many rows have been deleted for date. I was thinking in
> > creating a function, any recommendations?
>
>
> Copy and drop old table. If you delete you will have a massive problem
> with a bloated table and vacuum will not help unless you expect the
> table to grow to this size regulally otherwise vacuum full will take
> ages.
>
> Peter.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org

Browse pgsql-performance by date

  From Date Subject
Next Message Joost Kraaijeveld 2006-11-26 11:24:17 When to vacuum a table?
Previous Message Peter Childs 2006-11-25 15:45:19 Massive delete of rows, how to proceed?