1/*-------------------------------------------------------------------------
4 * Generalized tuple sorting routines.
6 * This module handles sorting of heap tuples, index tuples, or single
7 * Datums (and could easily support other kinds of sortable objects,
8 * if necessary). It works efficiently for both small and large amounts
9 * of data. Small amounts are sorted in-memory using qsort(). Large
10 * amounts are sorted using temporary files and a standard external sort
11 * algorithm. Parallel sorts use a variant of this external sort
12 * algorithm, and are typically only used for large amounts of data.
14 * Portions Copyright (c) 1996-2025, PostgreSQL Global Development Group
15 * Portions Copyright (c) 1994, Regents of the University of California
17 * src/include/utils/tuplesort.h
19 *-------------------------------------------------------------------------
35 * Tuplesortstate and Sharedsort are opaque types whose details are not
36 * known outside tuplesort.c.
42 * Tuplesort parallel coordination state, allocated by each participant in
43 * local memory. Participant caller initializes everything. See usage notes
48 /* Worker process? If not, must be leader. */
52 * Leader-process-passed number of participants known launched (workers
53 * set this to -1). Includes state within leader needed for it to
54 * participate as a worker, if any.
58 /* Private opaque state (points to shared memory) */
65 * Data structures for reporting sort statistics. Note that
66 * TuplesortInstrumentation can't contain any pointers because we
67 * sometimes put it in shared memory.
69 * The parallel-sort infrastructure relies on having a zero TuplesortMethod
70 * to indicate that a worker never did anything, so we assign zero to
71 * SORT_TYPE_STILL_IN_PROGRESS. The other values of this enum can be
72 * OR'ed together to represent a situation where different workers used
73 * different methods, so we need a separate bit for each one. Keep the
74 * NUM_TUPLESORTMETHODS constant in sync with the number of bits!
85 #define NUM_TUPLESORTMETHODS 4
93/* Bitwise option flags for tuple sorts */
94 #define TUPLESORT_NONE 0
96/* specifies whether non-sequential access to the sort result is required */
97 #define TUPLESORT_RANDOMACCESS (1 << 0)
99/* specifies if the tuplesort is able to support bounded sorts */
100 #define TUPLESORT_ALLOWBOUNDED (1 << 1)
103 * For bounded sort, tuples get pfree'd when they fall outside of the bound.
104 * When bounded sorts are not required, we can use a bump context for tuple
105 * allocation as there's no risk that pfree will ever be called for a tuple.
106 * Define a macro to make it easier for code to figure out if we're using a
109 #define TupleSortUseBumpTupleCxt(opt) (((opt) & TUPLESORT_ALLOWBOUNDED) == 0)
119 * The objects we actually sort are SortTuple structs. These contain
120 * a pointer to the tuple proper (might be a MinimalTuple or IndexTuple),
121 * which is a separate palloc chunk --- we assume it is just one chunk and
122 * can be freed by a simple pfree() (except during merge, where we use a
123 * simple slab allocator, and during a non-bounded sort where we use a bump
124 * allocator). SortTuples also contain the tuple's first key column in
125 * Datum/nullflag format, and a source/input tape number that tracks which
126 * tape each heap element/slot belongs to during merging.
128 * Storing the first key column lets us save heap_getattr or index_getattr
129 * calls during tuple comparisons. We could extract and save all the key
130 * columns not just the first, but this would increase code complexity and
131 * overhead, and wouldn't actually save any comparison cycles in the common
132 * case where the first key determines the comparison result. Note that
133 * for a pass-by-reference datatype, datum1 points into the "tuple" storage.
135 * There is one special case: when the sort support infrastructure provides an
136 * "abbreviated key" representation, where the key is (typically) a pass by
137 * value proxy for a pass by reference type. In this case, the abbreviated key
138 * is stored in datum1 in place of the actual first key column.
140 * When sorting single Datums, the data value is represented directly by
141 * datum1/isnull1 for pass by value types (or null values). If the datatype is
142 * pass-by-reference and isnull1 is false, then "tuple" points to a separately
143 * palloc'd data value, otherwise "tuple" is NULL. The value of datum1 is then
144 * either the same pointer as "tuple", or is an abbreviated key value as
145 * described above. Accordingly, "tuple" is always used in preference to
146 * datum1 as the authoritative value for pass-by-reference cases.
160 * The public part of a Tuple sort operation state. This data structure
161 * contains the definition of sort-variant-specific interface methods and
162 * the part of Tuple sort operation state required by their implementations.
167 * These function pointers decouple the routines that must know what kind
168 * of tuple we are sorting from the routines that don't need to know it.
169 * They are set up by the tuplesort_begin_xxx routines.
171 * Function to compare two tuples; result is per qsort() convention, ie:
172 * <0, 0, >0 according as a<b, a=b, a>b. The API must match
173 * qsort_arg_comparator.
178 * Fall back to the full tuple for comparison, but only compare the first
179 * sortkey if it was abbreviated. Otherwise, only compare second and later
185 * Alter datum1 representation in the SortTuple's array back from the
186 * abbreviated key to the first column value.
192 * Function to write a stored tuple onto tape. The representation of the
193 * tuple on tape need not be the same as it is in memory.
199 * Function to read a stored tuple from tape back into memory. 'len' is
200 * the already-read length of the stored tuple. The tuple is allocated
201 * from the slab memory arena, or is palloc'd, see
202 * tuplesort_readtup_alloc().
208 * Function to do some specific release of resources for the sort variant.
209 * In particular, this function should free everything stored in the "arg"
210 * field, which wouldn't be cleared on reset of the Tuple sort memory
211 * contexts. This can be NULL if nothing specific needs to be done.
216 * The subsequent fields are used in the implementations of the functions
220 * persists across multiple batches */
225 * Whether SortTuple's datum1 and isnull1 members are maintained by the
226 * above routines. If not, some sort specializations are disabled.
231 * The sortKeys variable is used by every case other than the hash index
232 * case; it is set by tuplesort_begin_xxx. tupDesc is only used by the
233 * MinimalTuple and CLUSTER routines, though.
235 int nKeys;
/* number of columns in sort key */
239 * This variable is shared by the single-key MinimalTuple case and the
240 * Datum case (which both use qsort_ssup()). Otherwise, it's NULL. The
241 * presence of a value in this field is also checked by various sort
242 * specialization functions as an optimization when comparing the leading
243 * key in a tiebreak situation to determine if there are any subsequent
248 int sortopt;
/* Bitmask of flags used to setup sort */
250 bool tuples;
/* Can SortTuple.tuple ever be set? */
252 void *
arg;
/* Specific information for the sort variant */
255/* Sort parallel code from state for sort__start probes */
256 #define PARALLEL_SORT(coordinate) (coordinate == NULL || \
257 (coordinate)->sharedsort == NULL ? 0 : \
258 (coordinate)->isWorker ? 1 : 2)
260 #define TuplesortstateGetPublic(state) ((TuplesortPublic *) state)
262/* When using this macro, beware of double evaluation of len */
263 #define LogicalTapeReadExact(tape, ptr, len) \
265 if (LogicalTapeRead(tape, ptr, len) != (size_t) (len)) \
266 elog(ERROR, "unexpected end of data"); \
270 * We provide multiple interfaces to what is essentially the same code,
271 * since different callers have different data to be sorted and want to
272 * specify the sort key information differently. There are two APIs for
273 * sorting HeapTuples and two more for sorting IndexTuples. Yet another
274 * API supports sorting bare Datums.
276 * Serial sort callers should pass NULL for their coordinate argument.
278 * The "heap" API actually stores/sorts MinimalTuples, which means it doesn't
279 * preserve the system columns (tuple identity and transaction visibility
280 * info). The sort keys are specified by column numbers within the tuples
281 * and sort operator OIDs. We save some cycles by passing and returning the
282 * tuples in TupleTableSlots, rather than forming actual HeapTuples (which'd
283 * have to be converted to MinimalTuples). This API works well for sorts
284 * executed as parts of plan trees.
286 * The "cluster" API stores/sorts full HeapTuples including all visibility
287 * info. The sort keys are specified by reference to a btree index that is
288 * defined on the relation to be sorted. Note that putheaptuple/getheaptuple
289 * go with this API, not the "begin_heap" one!
291 * The "index_btree" API stores/sorts IndexTuples (preserving all their
292 * header fields). The sort keys are specified by a btree index definition.
294 * The "index_hash" API is similar to index_btree, but the tuples are
295 * actually sorted by their hash codes not the raw data.
297 * The "index_brin" API is similar to index_btree, but the tuples are
298 * BrinTuple and are sorted by their block number not the raw data.
300 * Parallel sort callers are required to coordinate multiple tuplesort states
301 * in a leader process and one or more worker processes. The leader process
302 * must launch workers, and have each perform an independent "partial"
303 * tuplesort, typically fed by the parallel heap interface. The leader later
304 * produces the final output (internally, it merges runs output by workers).
306 * Callers must do the following to perform a sort in parallel using multiple
309 * 1. Request tuplesort-private shared memory for n workers. Use
310 * tuplesort_estimate_shared() to get the required size.
311 * 2. Have leader process initialize allocated shared memory using
312 * tuplesort_initialize_shared(). Launch workers.
313 * 3. Initialize a coordinate argument within both the leader process, and
314 * for each worker process. This has a pointer to the shared
315 * tuplesort-private structure, as well as some caller-initialized fields.
316 * Leader's coordinate argument reliably indicates number of workers
317 * launched (this is unused by workers).
318 * 4. Begin a tuplesort using some appropriate tuplesort_begin* routine,
319 * (passing the coordinate argument) within each worker. The workMem
320 * arguments need not be identical. All other arguments should match
322 * 5. tuplesort_attach_shared() should be called by all workers. Feed tuples
323 * to each worker, and call tuplesort_performsort() within each when input
325 * 6. Call tuplesort_end() in each worker process. Worker processes can shut
326 * down once tuplesort_end() returns.
327 * 7. Begin a tuplesort in the leader using the same tuplesort_begin*
328 * routine, passing a leader-appropriate coordinate argument (this can
329 * happen as early as during step 3, actually, since we only need to know
330 * the number of workers successfully launched). The leader must now wait
331 * for workers to finish. Caller must use own mechanism for ensuring that
332 * next step isn't reached until all workers have called and returned from
333 * tuplesort_performsort(). (Note that it's okay if workers have already
334 * also called tuplesort_end() by then.)
335 * 8. Call tuplesort_performsort() in leader. Consume output using the
336 * appropriate tuplesort_get* routine. Leader can skip this step if
337 * tuplesort turns out to be unnecessary.
338 * 9. Call tuplesort_end() in leader.
340 * This division of labor assumes nothing about how input tuples are produced,
341 * but does require that caller combine the state of multiple tuplesorts for
342 * any purpose other than producing the final output. For example, callers
343 * must consider that tuplesort_get_stats() reports on only one worker's role
344 * in a sort (or the leader's role), and not statistics for the sort as a
347 * Note that callers may use the leader process to sort runs as if it was an
348 * independent worker process (prior to the process performing a leader sort
349 * to produce the final sorted output). Doing so only requires a second
350 * "partial" tuplesort within the leader process, initialized like that of a
351 * worker process. The steps above don't touch on this directly. The only
352 * difference is that the tuplesort_attach_shared() call is never needed within
353 * leader process, because the backend as a whole holds the shared fileset
354 * reference. A worker Tuplesortstate in leader is expected to do exactly the
355 * same amount of total initial processing work as a worker process
356 * Tuplesortstate, since the leader process has nothing else to do before
359 * Note that only a very small amount of memory will be allocated prior to
360 * the leader state first consuming input, and that workers will free the
361 * vast majority of their memory upon returning from tuplesort_performsort().
362 * Callers can rely on this to arrange for memory to be used in a way that
363 * respects a workMem-style budget across an entire parallel sort operation.
365 * Callers are responsible for parallel safety in general. However, they
366 * can at least rely on there being no parallel safety hazards within
367 * tuplesort, because tuplesort thinks of the sort as several independent
368 * sorts whose results are combined. Since, in general, the behavior of
369 * sort operators is immutable, caller need only worry about the parallel
370 * safety of whatever the process is through which input tuples are
371 * generated (typically, caller uses a parallel heap scan).
404 * These routines may only be called if TUPLESORT_RANDOMACCESS was specified
405 * during tuplesort_begin_*. Additionally backwards scan in gettuple/getdatum
406 * also require TUPLESORT_RANDOMACCESS. Note that parallel sorts do not
407 * support random access.
416/* tuplesortvariants.c */
420 Oid *sortOperators,
Oid *sortCollations,
421 bool *nullsFirstFlags,
431 bool uniqueNullsNotDistinct,
452 Oid sortOperator,
Oid sortCollation,
480#endif /* TUPLESORT_H */
static Datum values[MAXATTR]
static void freestate(struct nfa *nfa, struct state *s)
TuplesortMethod sortMethod
TuplesortSpaceType spaceType
MemoryContext maincontext
MemoryContext tuplecontext
MemoryContext sortcontext
SortTupleComparator comparetup
SortTupleComparator comparetup_tiebreak
IndexTuple tuplesort_getindextuple(Tuplesortstate *state, bool forward)
void tuplesort_rescan(Tuplesortstate *state)
void tuplesort_performsort(Tuplesortstate *state)
struct SortCoordinateData SortCoordinateData
int tuplesort_merge_order(int64 allowedMem)
Tuplesortstate * tuplesort_begin_index_gin(Relation heapRel, Relation indexRel, int workMem, SortCoordinate coordinate, int sortopt)
void tuplesort_initialize_shared(Sharedsort *shared, int nWorkers, dsm_segment *seg)
HeapTuple tuplesort_getheaptuple(Tuplesortstate *state, bool forward)
void tuplesort_putdatum(Tuplesortstate *state, Datum val, bool isNull)
GinTuple * tuplesort_getgintuple(Tuplesortstate *state, Size *len, bool forward)
void tuplesort_reset(Tuplesortstate *state)
void tuplesort_putindextuplevalues(Tuplesortstate *state, Relation rel, ItemPointer self, const Datum *values, const bool *isnull)
bool tuplesort_skiptuples(Tuplesortstate *state, int64 ntuples, bool forward)
void tuplesort_puttupleslot(Tuplesortstate *state, TupleTableSlot *slot)
Tuplesortstate * tuplesort_begin_index_brin(int workMem, SortCoordinate coordinate, int sortopt)
Tuplesortstate * tuplesort_begin_heap(TupleDesc tupDesc, int nkeys, AttrNumber *attNums, Oid *sortOperators, Oid *sortCollations, bool *nullsFirstFlags, int workMem, SortCoordinate coordinate, int sortopt)
bool tuplesort_used_bound(Tuplesortstate *state)
Tuplesortstate * tuplesort_begin_cluster(TupleDesc tupDesc, Relation indexRel, int workMem, SortCoordinate coordinate, int sortopt)
BrinTuple * tuplesort_getbrintuple(Tuplesortstate *state, Size *len, bool forward)
Tuplesortstate * tuplesort_begin_index_btree(Relation heapRel, Relation indexRel, bool enforceUnique, bool uniqueNullsNotDistinct, int workMem, SortCoordinate coordinate, int sortopt)
Tuplesortstate * tuplesort_begin_index_gist(Relation heapRel, Relation indexRel, int workMem, SortCoordinate coordinate, int sortopt)
Size tuplesort_estimate_shared(int nWorkers)
struct SortCoordinateData * SortCoordinate
void tuplesort_get_stats(Tuplesortstate *state, TuplesortInstrumentation *stats)
bool tuplesort_gettupleslot(Tuplesortstate *state, bool forward, bool copy, TupleTableSlot *slot, Datum *abbrev)
Tuplesortstate * tuplesort_begin_common(int workMem, SortCoordinate coordinate, int sortopt)
void tuplesort_end(Tuplesortstate *state)
void tuplesort_putgintuple(Tuplesortstate *state, GinTuple *tuple, Size size)
void tuplesort_markpos(Tuplesortstate *state)
void tuplesort_puttuple_common(Tuplesortstate *state, SortTuple *tuple, bool useAbbrev, Size tuplen)
const char * tuplesort_space_type_name(TuplesortSpaceType t)
bool tuplesort_gettuple_common(Tuplesortstate *state, bool forward, SortTuple *stup)
void tuplesort_attach_shared(Sharedsort *shared, dsm_segment *seg)
Tuplesortstate * tuplesort_begin_datum(Oid datumType, Oid sortOperator, Oid sortCollation, bool nullsFirstFlag, int workMem, SortCoordinate coordinate, int sortopt)
void tuplesort_putbrintuple(Tuplesortstate *state, BrinTuple *tuple, Size size)
const char * tuplesort_method_name(TuplesortMethod m)
struct TuplesortInstrumentation TuplesortInstrumentation
void tuplesort_restorepos(Tuplesortstate *state)
Tuplesortstate * tuplesort_begin_index_hash(Relation heapRel, Relation indexRel, uint32 high_mask, uint32 low_mask, uint32 max_buckets, int workMem, SortCoordinate coordinate, int sortopt)
void * tuplesort_readtup_alloc(Tuplesortstate *state, Size tuplen)
int(* SortTupleComparator)(const SortTuple *a, const SortTuple *b, Tuplesortstate *state)
@ SORT_TYPE_EXTERNAL_SORT
@ SORT_TYPE_TOP_N_HEAPSORT
@ SORT_TYPE_STILL_IN_PROGRESS
@ SORT_TYPE_EXTERNAL_MERGE
void tuplesort_putheaptuple(Tuplesortstate *state, HeapTuple tup)
bool tuplesort_getdatum(Tuplesortstate *state, bool forward, bool copy, Datum *val, bool *isNull, Datum *abbrev)
void tuplesort_set_bound(Tuplesortstate *state, int64 bound)