Skip site navigation (1) Skip section navigation (2)

Re: Aggregate-function space leakage

From: Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org, Chris Spotts <rfusca(at)gmail(dot)com>
Subject: Re: Aggregate-function space leakage
Date: 2009-07-24 07:09:29
Message-ID: e08cc0400907240009h1f3b44f9tbccbe765f22bb32c@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
2009/7/24 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> I think that WindowAgg does not need any changes because it already does
> MemoryContextResetAndDeleteChildren(winstate->wincontext) at partition
> boundaries.  Hitoshi, do you agree?
>

I do. Looking closer, temporal space management of Agg is getting
similar to WindowAgg's partition localMemory strategy. We might be
able to get them one. Anyway, the choice sounds better now, though I
will test array_agg more.

Regards,

-- 
Hitoshi Harada

In response to

pgsql-hackers by date

Next:From: Magnus HaganderDate: 2009-07-24 07:23:01
Subject: Re: Determining client_encoding from client locale
Previous:From: mahendra chavanDate: 2009-07-24 06:27:51
Subject: Re: query decorrelation in postgres

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group