| From: | "Robert Bedell" <robert(at)friendlygenius(dot)com> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "'Hannu Krosing'" <hannu(at)tm(dot)ee>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: OLAP CUBE/ROLLUP Operators and GROUP BY grouping sets |
| Date: | 2003-12-18 04:25:34 |
| Message-ID: | 200312172325823.SM00984@xavier |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thanks for the pointers!
> > The documentation points to the
> > 'sort_mem' parameter for this, but the code doesn't look to actually
> > implement that yet.
>
> Well, yeah, that's sort of exactly the point ... it's considered during
> planning but the executor code has no fallback if the planner guesses
> wrong.
Yep. The doc is wishful thinking then ;) I was just verifying that.
> > 4) Should LookupTupleHashEntry() be worried about the pointers it
> > receives...similarly for hash_search()?
Was wondering how safe it was to write hashed data to disk.. given your
suggestions (and the obvious necessity) pretty safe, but it requires some
handling. My bad.
Cheers!
Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-12-18 04:38:26 | Re: OLAP CUBE/ROLLUP Operators and GROUP BY grouping sets |
| Previous Message | Tom Lane | 2003-12-18 04:18:51 | Re: OLAP CUBE/ROLLUP Operators and GROUP BY grouping sets |