fix(db-postgres): add filenameCompoundIndex baseIndexes for upload collections#15182
Merged
DanRibbens merged 3 commits intopayloadcms:mainfrom Jan 13, 2026
Merged
fix(db-postgres): add filenameCompoundIndex baseIndexes for upload collections#15182DanRibbens merged 3 commits intopayloadcms:mainfrom
DanRibbens merged 3 commits intopayloadcms:mainfrom
Conversation
tapartdev
changed the title
tapartdev
changed the title
r1tsuu
approved these changes
Jan 13, 2026
DanRibbens
approved these changes
Jan 13, 2026
Contributor
|
🚀 This is included in version v3.71.0 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
When using the filenameCompoundIndex property on an upload collection, this index was not being added to the database. By adding this rule, the compound index is now correctly applied.
What?
The filenameCompoundIndex property was ignored when defining upload collections, so compound indexes were not created in the database.
Why?
Without this index, queries that rely on the compound key (e.g., filename + some other field) are slower and may lead to unexpected duplicates.
How?
Updated the logic for creating upload collection indexes to include the filenameCompoundIndex rule. This ensures that the compound index is added to the database during collection setup.