Re: HOT question - insert/delete

The data isn't really historical, but some data have to be for e.g. some
regulations after a period of time. But all the available data should be
available for e.g. reporting. So partitioning doesn't make any sense
in this case, right?

Ciao,
Gerhard

--
http://www.wiesinger.com/

On Thu, 21 May 2009, Simon Riggs wrote:

>
> 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
>
>
> --
> 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
>