Re: Abbreviated keys for text cost model fix

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Jeremy Harris <jgh(at)wizmail(dot)org>
Cc: Arthur Silva <arthurprs(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Abbreviated keys for text cost model fix
Date: 2015-03-03 17:56:12
Message-ID: CAM3SWZTYVuaWG5gR3tpE9eRigpi78TFs0T9FJmYisX9pBM=eRw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 3, 2015 at 2:00 AM, Jeremy Harris <jgh(at)wizmail(dot)org> wrote:
> Yes; there seemed no advantage to any additional complexity.
> The merge consistently performs fewer comparisons than the
> quicksort, on random input - and many fewer if there are
> any sorted (or reverse-sorted) sections. However, it also
> consistently takes slightly longer (a few percent). I was
> unable to chase this down but assume it to be a cacheing
> effect. So I don't currently think it should replace the
> current sort for all use.

It's definitely caching effects. That's a very important consideration here.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2015-03-03 18:05:17 Re: Providing catalog view to pg_hba.conf file - Patch submission
Previous Message Bruce Momjian 2015-03-03 17:53:49 Re: Partitioning WIP patch