| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Gerhard Wiesinger <lists(at)wiesinger(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: HOT question - insert/delete |
| Date: | 2009-05-21 08:37:37 |
| Message-ID: | 1242895057.27960.245.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 2009-05-20 at 16:01 -0400, Merlin Moncure wrote:
> On Wed, May 20, 2009 at 3:11 PM, Gerhard Wiesinger <lists(at)wiesinger(dot)com> wrote:
> > Hello!
> >
> > Is HOT in 8.3 used in the following scenario:
> > INSERT ...
> > DELETE ...
> > at the same ratio.
> >
> > So for example current data is added every minute and all old data older
> > than 2 years are deleted.
> >
> > Would the heap be bloated or is this avoided by the HOT feature of 8.3 and
> > nearly kept constant?
>
> HOT doesn't help here...it only helps with updates and then only if
> you are updating fields that are not indexed.
Partial vacuum, in 8.4, will deal with this situation, though
partitioning does sound best for such clearly historical data.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gerhard Wiesinger | 2009-05-21 08:38:07 | Re: HOT question - insert/delete |
| Previous Message | Grzegorz Jaśkiewicz | 2009-05-21 08:34:16 | Re: HOT question - insert/delete |