| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Claudio Freire <klaussfreire(at)gmail(dot)com> |
| Subject: | Re: Tuplesort merge pre-reading |
| Date: | 2016-09-09 17:22:38 |
| Message-ID: | CAM3SWZRtp67vuY3cso2Pk8JbbqT4KJeRekZ1vy1Ltv6Fj3HmCg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Sep 9, 2016 at 5:25 AM, Greg Stark <stark(at)mit(dot)edu> wrote:
> Wow, this is really cool. We should do something like this for query
> execution too.
We should certainly do this for tuplestore.c, too. I've been meaning
to adopt it to use batch memory. I did look at it briefly, and recall
that it was surprisingly awkward because a surprisingly large number
of callers want to have memory that they can manage independently of
the lifetime of their tuplestore.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2016-09-09 17:51:41 | Re: [COMMITTERS] pgsql: Use LEFT JOINs in some system views in case referenced row doesn |
| Previous Message | Peter Geoghegan | 2016-09-09 16:50:22 | Re: Tuplesort merge pre-reading |