| From: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Atri Sharma <atri(dot)jiit(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Memory Accounting v11 |
| Date: | 2015-07-17 03:52:51 |
| Message-ID: | CAKJS1f_YnwRSCdbYkpQxX1bk4zu2_297rCFt66z2uqe7_GooqA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 16 July 2015 at 05:07, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> On Wed, 2015-07-15 at 12:59 +0530, Atri Sharma wrote:
>
> >
> > I think a heuristic would be more suited here and ignoring memory
> > consumption for internal types means that we are not making the memory
> > accounting useful for a set of usecases.
> >
> OK, I will drop this patch and proceed with the HashAgg patch, with a
> heuristic for internal types.
>
>
Should we mark the patch as "returned with feedback" in the commitfest app
then?
--
David Rowley http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2015-07-17 04:26:55 | Re: proposal: multiple psql option -c |
| Previous Message | Tom Lane | 2015-07-17 03:49:42 | Re: Memory prefetching while sequentially fetching from SortTuple array, tuplestore |