AWS AmazonRDS medium security documentation change
Summary
Added release notes for Aurora PostgreSQL Limitless Database 16.8.103 with bug fixes including privilege grant issues and query optimizations
Security assessment
The fix for privilege grants failing when granting to 'public' addresses a potential security concern where improper privilege management could lead to unauthorized access. Granting privileges to public is a security-sensitive operation and fixing related errors helps prevent misconfigurations.
Diff
diff --git a/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/limitless-updates.md b/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/limitless-updates.md index bea328699..570675baf 100644 --- a//AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/limitless-updates.md +++ b//AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/limitless-updates.md @@ -150,0 +151,2 @@ This version of Aurora PostgreSQL Limitless Database is compatible with PostgreS + * Aurora PostgreSQL Limitless Database 16.8.103, October 30, 2025 + @@ -159,0 +162,17 @@ This version of Aurora PostgreSQL Limitless Database is compatible with PostgreS +### Aurora PostgreSQL Limitless Database 16.8.103, October 30, 2025 + +**Bug fixes** + + * Fixed an issue with privilege grants which failed with `invalid role OID: 0` when all privileges are `GRANT`ed to public. + + * Fixed an issue with `SELECT` queries with type casts which failed with `cannot cast type cstring to text[]`. + + * Fixed an issue with `CREATE DATABASE` which failed with `connection_limit requires an integer value` when also setting `connection_limit`. + + * Fixed incorrect result when selecting `tableoid` system column. The `tableoid` is the OID of the table, which is a distinct identification given to the database object by a given system. If the query is eligible for Single Shard Optimization, the `tableoid` will be obtained from the Shard. Otherwise, the `tableoid` will be obtained from the connected router. Different routers may result in different `tableoid` for the same query. + + * Fixed one edge case in resolving prepared transaction. + + + +