| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| 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:55:39 |
| Message-ID: | CAH2-WzkH2kk4yj6qq9BAAVb9tWPUMaEXq7TQkAsZ1BSD=Ei=fQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 6, 2017 at 2:47 PM, Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
>> 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.
Thanks for looking into it.
I suppose that the solution is to change the 9.6 release notes to no
longer have a replacement_sort_tuples link. Anyone else have an
opinion on that?
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Omar Kilani | 2017-09-06 22:33:56 | Re: Replication vs. float timestamps is a disaster |
| Previous Message | Tom Lane | 2017-09-06 21:52:56 | Re: Minor code improvement to postgresGetForeignPlan |