From 03d1a4cf3b4f8bc4dd19aca4fca0576df3e7dbf7 Mon Sep 17 00:00:00 2001 From: "Ru, Li Yi" Date: Fri, 22 Nov 2024 12:24:15 +0000 Subject: [PATCH] rds_umn_20241122 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Reviewed-by: Székely, Ond Co-authored-by: Ru, Li Yi Co-committed-by: Ru, Li Yi --- docs/rds/umn/en-us_topic_0000001990102985.html | 2 +- docs/rds/umn/rds_09_0045.html | 10 +++++----- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/rds/umn/en-us_topic_0000001990102985.html b/docs/rds/umn/en-us_topic_0000001990102985.html index 46149fcb..20fca990 100644 --- a/docs/rds/umn/en-us_topic_0000001990102985.html +++ b/docs/rds/umn/en-us_topic_0000001990102985.html @@ -5,7 +5,7 @@

Autoscaling up the storage space of a read replica does not affect that of the primary DB instance. Therefore, you can separately autoscale read replicas to meet service requirements. New storage space of read replicas after autoscaling up must be greater than or equal to that of the primary DB instance.

Constraints

  • The maximum allowed storage is 4,000 GB.
-
  • For primary/standby DB instances, autoscaling the storage for the primary DB instance will also autoscale the storage for the standby DB instance.
  • Storage autoscaling is unavailable when the DB instance is changing instance class or rebooting.
  • Storage of RDS for SQL Server instances cannot be scaled down. Exercise caution when enabling autoscaling.
  • There is an upper limit on autoscaling. For example, if an instance scales out for multiple times within a short period of time due to a sharp increase of temporary databases or log files, to prevent the storage from getting full, you can shrink the databases or log files to reduce the storage usage.
+
  • For primary/standby DB instances, autoscaling the storage for the primary DB instance will also autoscale the storage for the standby DB instance.
  • Storage autoscaling is unavailable when the DB instance is changing instance class or rebooting.
  • Storage of RDS for SQL Server instances cannot be scaled down. Exercise caution when enabling autoscaling.
  • There is an upper limit on storage autoscaling. A maximum of two scale-ups are allowed within one hour and a maximum of five scale-ups within one day. If an instance scales up multiple times within a short period of time due to a sharp increase of temporary databases or log files, to reduce the storage usage, you can shrink the databases or log files.

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region.
  3. Click Service List. Under Database, click Relational Database Service.
  4. On the Instances page, click the target DB instance or read replica (click in front of a DB instance to locate the read replica).
  5. In the Storage Space area, click Configure Autoscaling.
  6. In the displayed dialog box, set the following parameters.

    - - - - -
    Table 1 Parameter description

    Parameter

    diff --git a/docs/rds/umn/rds_09_0045.html b/docs/rds/umn/rds_09_0045.html index e25b4a25..3b5fefa1 100644 --- a/docs/rds/umn/rds_09_0045.html +++ b/docs/rds/umn/rds_09_0045.html @@ -867,15 +867,15 @@

    -

    0.5.1

    +

    0.7.0

    0.5.1

    +

    0.7.0

    0.5.1

    +

    0.7.0

    0.5.1

    +

    0.7.0

    0.6.1

    +

    0.7.0

    plpgsql