mirror of
https://github.com/postgres/postgres.git
synced 2026-04-03 00:05:41 -04:00
CLUSTER sort won't use the datum1 SortTuple field when clustering against an index whose leading key is an expression. This makes it unsafe to use the abbreviated keys optimization, which was missed by the logic that sets up SortSupport state. Affected tuplesorts output tuples in a completely bogus order as a result (the wrong SortSupport based comparator was used for the leading attribute). This issue is similar to the bug fixed on the master branch by recent commit |
||
|---|---|---|
| .. | ||
| logtape.c | ||
| Makefile | ||
| sharedtuplestore.c | ||
| sortsupport.c | ||
| tuplesort.c | ||
| tuplestore.c | ||