From: | Grzegorz Jaśkiewicz <gryzman(at)gmail(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:34:16 |
Message-ID: | 2f4958ff0905210134oc594f02ha437723f50937cdc@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, May 20, 2009 at 9:01 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> 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).
on that note, does HOT works in case I have TOASTed columns ? bytea,
varchar(), etc ?
--
GJ
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2009-05-21 08:37:37 | Re: HOT question - insert/delete |
Previous Message | Sofer, Yuval | 2009-05-21 08:04:55 | compilation test fails |