AWS redshift documentation change
Summary
Added information about IANA time zone database updates affecting timestamp conversions after August 2025
Security assessment
Time zone calculation changes impact data consistency but do not directly address security vulnerabilities or weaknesses.
Diff
diff --git a/redshift/latest/mgmt/behavior-changes.md b/redshift/latest/mgmt/behavior-changes.md index d18c381f2..464dce019 100644 --- a//redshift/latest/mgmt/behavior-changes.md +++ b//redshift/latest/mgmt/behavior-changes.md @@ -20,0 +21,2 @@ The following describes upcoming behavior changes. + * Amazon Redshift won’t support functions that access consumer information through datasharing after February 16, 2026 + @@ -46,0 +49,4 @@ For information on creating and using Lambda UDFs, see [Scalar Lambda UDFs](http +### Amazon Redshift won’t support functions that access consumer information through datasharing after February 16, 2026 + +Starting February 16, 2026, Amazon Redshift will no longer support the usage of `user_is_member_of` and related functions that access consumer user, role, or group information through datasharing. + @@ -98,0 +105,2 @@ We recommend using the latest version of the Amazon Redshift driver [3] if possi + * Amazon Redshift uses up-to-date IANA time zone database after Aug 26, 2025 + @@ -111,0 +120,35 @@ We recommend using the latest version of the Amazon Redshift driver [3] if possi +### Amazon Redshift uses up-to-date IANA time zone database after Aug 26, 2025 + +Beginning Aug 26, 2025, Amazon Redshift calculates time zones by adopting the latest IANA time zone database patches. This change alters how date and time conversions function for certain time zones and time periods. This update affects explicit time zone conversions, such as those performed with the [CONVERT_TIMEZONE](https://docs.aws.amazon.com/redshift/latest/dg/CONVERT_TIMEZONE.html) function or the [TIMEZONE](https://docs.aws.amazon.com/redshift/latest/dg/r_TIMEZONE.html) and [AT TIME ZONE](https://docs.aws.amazon.com/redshift/latest/dg/r_AT_TIME_ZONE.html) commands, as well as implicit conversions that occur during type casting operations, particularly between [TIMESTAMP](https://docs.aws.amazon.com/redshift/latest/dg/r_Datetime_types.html#r_Datetime_types-timestamp) and [TIMESTAMPTZ](https://docs.aws.amazon.com/redshift/latest/dg/r_Datetime_types.html#r_Datetime_types-timestamptz) formats. + +The following is a list of updates for time zone and time period combinations: + + * Time zones now correctly observe daylight saving time (DST) after year 2038. Previously, no time zone observed DST after 2038. + + * The `America/Toronto` time zone, and the time zones that link to it, have DST switch in 1947-1950 at 2 AM local time instead of at midnight. + + * Amazon Redshift now correctly reflects local mean time (LMT) for periods before standardization for all time zones. This period is specific to a time zone, with most time zones switching to standardization before mid-19th century. + + * `EET`, `CET`, `WET` and `MET` are now treated as normal time zones instead of abbreviations. + + * The following time zone names no longer exist in Amazon Redshift: + + * `Asia/Riyadh87` + + * `Asia/Riyadh88` + + * `Asia/Riyadh89` + + * `Mideast/Riyadh87` + + * `Mideast/Riyadh88` + + * `Mideast/Riyadh89` + + * `US/Pacific-New` + + + + +For more information on the IANA time zone database, see [IANA time zones](https://www.iana.org/time-zones). + @@ -131,0 +175,9 @@ For questions or concerns, contact AWS support at the following link: [AWS Suppo +###### Topics + + * Query monitoring changes effective after May 2, 2025 + + * Security changes effective after January 10, 2025 + + + +