| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Polyphase merge is obsolete |
| Date: | 2016-10-14 23:30:58 |
| Message-ID: | CAM3SWZR4MQbXFuT1Q+TyRYSPbNVkHsMx+SfVQnHqFLi6tNQoAw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 12, 2016 at 10:16 AM, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
> Let's switch over to a simple k-way balanced merge. Because it's simpler. If
> you're severely limited on memory, like when sorting 1GB of data with
> work_mem='1MB' or less, it's also slightly faster. I'm not too excited about
> the performance aspect, because in the typical case of a single-pass merge,
> there's no difference. But it would be worth changing on simplicity grounds,
> since we're mucking around in tuplesort.c anyway.
This analysis seems sound. I suppose we might as well simplify things
while we're at it.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2016-10-14 23:51:58 | Re: pg_basebackup stream xlog to tar |
| Previous Message | Tatsuo Ishii | 2016-10-14 21:50:20 | Re: [COMMITTERS] pgsql: Remove spurious word. |