Re: Using quicksort for every external sort run - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Using quicksort for every external sort run
Date
Msg-id CAM3SWZQj4i=ZMbxdpjdZjR-CY+OvLpb0=K5exW2Gs5LDUu8tFQ@mail.gmail.com
Whole thread Raw
In response to Re: Using quicksort for every external sort run  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
List pgsql-hackers
<p dir="ltr">I just mean that, as you say, trace_sort is described in the documentation. <p dir="ltr">I don't think
we'llend up with any kind of cost model here, so where that would need to happen is only an academic matter. The create
indexparameter would only be an option for the DBA. That's about the only case I can see working for replacement
selection:where indexes can be created with very little memory quickly, by optimistically starting to write out the
startof the final index representation almost immediately, before most of the underlying table has even been read in.
<pdir="ltr">--<br /> Peter Geoghegan 

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: More stable query plans via more predictable column statistics
Next
From: Jeff Janes
Date:
Subject: Re: snapshot too old, configured by time