Re: [PERFORM] bad performance - Mailing list pgsql-performance

From Jeremy Harris
Subject Re: [PERFORM] bad performance
Date
Msg-id 9d8bede6-ce73-50a1-a6bc-53b77d168168@wizmail.org
Whole thread Raw
In response to Re: [PERFORM] bad performance  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
On 17/12/16 23:04, Tom Lane wrote:
> so that you don't need to use
> SELECT DISTINCT?  The sort/unique steps needed to do DISTINCT are
> eating a large part of the runtime,

Does a hash join result in a set of buckets that are then read out
in order?  It might, unless the sort method takes advantage of
partially-sorted inout, be cheaper (by log(num-buckets)) to sort/uniq
each bucket separately (and it would parallelize, too).
--
Cheers,
  Jeremy



pgsql-performance by date:

Previous
From: ProPAAS DBA
Date:
Subject: Re: [PERFORM] How to vacuum entire database excluding some tables inPostgreSQL9.1.
Next
From: Dinesh Chandra 12108
Date:
Subject: [PERFORM] Invalid page header in block 25561983 of relation pg_tblspc