| From: | Qingqing Zhou <zhouqq(dot)postgres(at)gmail(dot)com> |
|---|---|
| To: | CK Tan <cktan(at)vitessedata(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Memory Accounting v11 |
| Date: | 2015-07-02 22:09:19 |
| Message-ID: | CAJjS0u0GuSdWpFhLHiciEG9SP7bz+oRBoaSWXfebBUsjv_Sepg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jul 2, 2015 at 11:37 AM, CK Tan <cktan(at)vitessedata(dot)com> wrote:
>
> I am sorry to ask questions unrelated to the subject, but how is tracking
> memory going to fix the HashAgg blow up problem? Is there a plan to make
> HashAgg not blow up (i.e. spill the hash table)?
>
Your question is probably answered here:
http://www.postgresql.org/message-id/1407012053.15301.53.camel@jeff-desktop
Regards,
Qingqing
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-07-02 22:15:26 | Re: pg_restore -t should match views, matviews, and foreign tables |
| Previous Message | Martijn van Oosterhout | 2015-07-02 22:05:24 | WAL logging problem in 9.4.3? |