| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Gerhard Wiesinger <lists(at)wiesinger(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: HOT question - insert/delete |
| Date: | 2009-05-20 20:01:53 |
| Message-ID: | b42b73150905201301j128dbba4mc29f808cc2ddcb0a@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergey Samokhin | 2009-05-20 20:41:33 | How should I deal with disconnects during insert? |
| Previous Message | Harald Fuchs | 2009-05-20 19:41:35 | Re: Help with join syntax sought |