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 M
Are there any plans to support this kind of scenario?
Ciao,
Gerhard
--
http://www.wiesinger.com/
On Wed, 20 May 2009, Merlin Moncure wrote:
On Wed, May 20, 2009 at 3:11 PM, Gerhard Wiesinger wrote:
Hello!
Is HOT in 8.3 used in the following scenario:
INSERT ...
DELETE ...
at the same ra
On Wed, 2009-05-20 at 16:01 -0400, Merlin Moncure wrote:
> On Wed, May 20, 2009 at 3:11 PM, Gerhard Wiesinger
> 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 a
On Wed, May 20, 2009 at 9:01 PM, Merlin Moncure wrote:
> On Wed, May 20, 2009 at 3:11 PM, Gerhard Wiesinger
> 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
On Wed, May 20, 2009 at 3:11 PM, Gerhard Wiesinger 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