| From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Subject: | Re: The case for removing replacement selection sort |
| Date: | 2017-09-06 21:47:41 |
| Message-ID: | CAEepm=2qsv932DZWfMyBNhpfCrxtznV-2GCjST1gxqnY5bG02Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Sep 1, 2017 at 6:00 AM, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> On Wed, Aug 30, 2017 at 4:59 PM, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
>> I may submit the simple patch to remove replacement selection, if
>> other contributors are receptive. Apart from everything else, the
>> "incrementalism" of replacement selection works against cleverer batch
>> memory management of the type I just outlined, which seems like a
>> useful direction to take tuplesort in.
>
> I attach a patch to remove replacement selection, which I'll submit to CF 1.
This breaks the documentation build, because
doc/src/sgml/release-9.6.sgml still contains <xref
linkend="guc-replacement-sort-tuples"> but you removed that id.
--
Thomas Munro
http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-09-06 21:52:56 | Re: Minor code improvement to postgresGetForeignPlan |
| Previous Message | Tom Lane | 2017-09-06 21:37:32 | Re: merge psql ef/ev sf/sv handling functions |