Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit98b3743

Browse files
committed
Update comment.
The _bt_tuplecompare() function mentioned in comment hasn't existed for along time.Peter Geoghegan
1 parent284590e commit98b3743

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

‎src/backend/utils/sort/tuplesort.c

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3176,9 +3176,8 @@ comparetup_index_btree(const SortTuple *a, const SortTuple *b,
31763176
Tuplesortstate*state)
31773177
{
31783178
/*
3179-
* This is similar to _bt_tuplecompare(), but we have already done the
3180-
* index_getattr calls for the first column, and we need to keep track of
3181-
* whether any null fields are present. Also see the special treatment
3179+
* This is similar to comparetup_heap(), but expects index tuples. There
3180+
* is also special handling for enforcing uniqueness, and special treatment
31823181
* for equal keys at the end.
31833182
*/
31843183
ScanKeyscanKey=state->indexScanKey;

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp