| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Odd out of memory problem. |
| Date: | 2012-03-26 17:15:47 |
| Message-ID: | 12927.1332782147@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greg Stark <stark(at)mit(dot)edu> writes:
> I have a sketch for how to handle spilling hash aggregates to disk in
> my head. I'm not sure if it's worth the amount of complexity it would
> require but I'll poke around a bit and see if it works out well.
It'd be awfully nice if those could spill to disk. I think that
currently that's the only plan type where a misestimate can lead to
hard failure rather than just slower-than-you'd-like. Which is not
nice considering that the estimates are necessarily just estimates.
Could you give us a brain dump on the sketch? I've never seen how to
do it without unreasonable overhead.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2012-03-26 17:23:58 | Re: Odd out of memory problem. |
| Previous Message | Heikki Linnakangas | 2012-03-26 17:06:37 | Re: Odd out of memory problem. |