pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: andrew@pillette.com
To: pgsql-performance@postgresql.org
Subject: Re: Massive delete of rows, how to proceed?
Date: Sat, 25 Nov 2006 16:35:01 -0800
Message-ID: <200611260035.kAQ0Z1G02487@pillette.com> (raw)

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

"Peter Childs" <peterachilds@gmail.com> wrote ..
> On 24/11/06, Arnau <arnaulist@andromeiberica.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



view thread (4+ messages)  latest in thread

Message-ID: <200611260035.kAQ0Z1G02487@pillette.com>
Permalink:  ../200611260035.kAQ0Z1G02487@pillette.com/
Also on:    postgresql.org/message-id/200611260035.kAQ0Z1G02487@pillette.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: andrew@pillette.com
  Subject: Re: Massive delete of rows, how to proceed?
  In-Reply-To: <200611260035.kAQ0Z1G02487@pillette.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox