Skip site navigation (1) Skip section navigation (2)

Re: DELETE performance problem

From: Thom Brown <thombrown(at)gmail(dot)com>
To: Luca Tettamanti <kronos(dot)it(at)gmail(dot)com>
Cc: Jerry Champlin <jchamplin(at)absolute-performance(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: DELETE performance problem
Date: 2009-11-24 15:19:23
Message-ID: bddc86150911240719r358cafbv854cebb5748a969d@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
2009/11/24 Luca Tettamanti <kronos(dot)it(at)gmail(dot)com>

> On Tue, Nov 24, 2009 at 3:59 PM, Jerry Champlin
> <jchamplin(at)absolute-performance(dot)com> wrote:
> > You may want to consider using partitioning.  That way you can drop the
> > appropriate partition and never have the overhead of a delete.
>
> Hum, I don't think it's doable in my case; the partitioning is not
> know a priori. First t1 is fully populated, then the data is loaded
> and manipulated by my application, the result is stored in t2; only
> then I want to remove (part of) the data from t1.
>
> thanks,
> Luca
>
>
It's a shame there isn't a LIMIT option on DELETE so this can be done in
small batches.

Thom

In response to

Responses

pgsql-performance by date

Next:From: Lorenzo AllegrucciDate: 2009-11-24 15:32:25
Subject: Re: [PERFORM] Strange performance degradation
Previous:From: Luca TettamantiDate: 2009-11-24 15:14:46
Subject: Re: DELETE performance problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group