1 Answer
- Newest
- Most votes
- Most comments
0
Yes, this happens when you use FLOAT for the decimal data because it cannot store values of arbitrary precision. https://en.wikipedia.org/wiki/IEEE_754
I would generally always recommend using the DECIMAL datatype unless you have an existing application that has an unchangeable requirement for FLOAT, e.g., calculation expects FLOAT and output cannot change.
Additionally, by using DECIMAL you are able to use our new AZ64 compression encoding which will reduce the amount of storage needed and improve your query performance. https://aws.amazon.com/about-aws/whats-new/2019/10/amazon-redshift-introduces-az64-a-new-compression-encoding-for-optimized-storage-and-high-query-performance/
answered 5 years ago
Relevant content
- Accepted Answerasked 7 months ago
- Accepted Answerasked 5 years ago
- asked 7 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago