We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
According to https://github.com/awslabs/amazon-redshift-utils/blob/master/src/Investigations/EarlyMaterialization.md it is possible that encoded sorkeys can cause "sortkey skew" and lead to excessive block I/O with early materialization.
In:
The tables:
are created with explicit ZSTD encoding on the columns defined as primary sortkeys.
ZSTD
I believe these columns should have their encodings changed from ZSTD to RAW.
RAW
The text was updated successfully, but these errors were encountered:
Redshift/web: Change SORTKEY encoding to RAW (close #129)
16ca08d
Redshift web: Change SORTKEY encoding to RAW (close #129)
3d93c81
44853d1
fb4d589
No branches or pull requests
According to https://github.com/awslabs/amazon-redshift-utils/blob/master/src/Investigations/EarlyMaterialization.md it is possible that encoded sorkeys can cause "sortkey skew" and lead to excessive block I/O with early materialization.
In:
The tables:
are created with explicit
ZSTD
encoding on the columns defined as primary sortkeys.I believe these columns should have their encodings changed from
ZSTD
toRAW
.The text was updated successfully, but these errors were encountered: