| From: | Gerhard Wiesinger <lists(at)wiesinger(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Subject: | Re: HOT question - insert/delete |
| Date: | 2009-05-21 08:38:07 |
| Message-ID: | alpine.LFD.2.00.0905211037140.27998@bbs.intern |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Are there any plans to support this kind of scenario?
Ciao,
Gerhard
On Wed, 20 May 2009, 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. if your table has a
> rolling set of data, for example a log file...you probably want to
> look at table partitioning (either manual or built in).
>
> merlin
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sofer, Yuval | 2009-05-21 08:42:30 | compilation test fails |
| Previous Message | Simon Riggs | 2009-05-21 08:37:37 | Re: HOT question - insert/delete |