AWS dms documentation change
Summary
Updated documentation with grammatical corrections (contractions expanded to full forms like 'does not' instead of 'doesn't') and minor clarifications in PostgreSQL source configuration details. No functional changes to features or workflows.
Security assessment
Changes are purely grammatical/typographical with no references to vulnerabilities, security controls, or security-related configurations. Updates focus on readability rather than addressing security concerns.
Diff
diff --git a/dms/latest/userguide/CHAP_Source.PostgreSQL.md b/dms/latest/userguide/CHAP_Source.PostgreSQL.md index ff58baa92..93f4bbe53 100644 --- a//dms/latest/userguide/CHAP_Source.PostgreSQL.md +++ b//dms/latest/userguide/CHAP_Source.PostgreSQL.md @@ -284 +284 @@ You can use PostgreSQL's native logical replication feature to enable change dat -AWS DMS supports CDC for PostgreSQL tables with primary keys. If a table doesn't have a primary key, the write-ahead logs (WAL) don't include a before image of the database row. In this case, DMS can't update the table. Here, you can use additional configuration settings and use table replica identity as a workaround. However, this approach can generate extra logs. We recommend that you use table replica identity as a workaround only after careful testing. For more information, see Additional configuration settings when using a PostgreSQL database as a DMS source. +AWS DMS supports CDC for PostgreSQL tables with primary keys. If a table does not have a primary key, the write-ahead logs (WAL) don't include a before image of the database row. In this case, DMS can't update the table. Here, you can use additional configuration settings and use table replica identity as a workaround. However, this approach can generate extra logs. We recommend that you use table replica identity as a workaround only after careful testing. For more information, see Additional configuration settings when using a PostgreSQL database as a DMS source. @@ -361 +361 @@ The following procedure walks through this approach in more detail. - 1. Identify the logical replication slot used by an earlier replication task (a parent task) that you want to use as a start point. Then query the `pg_replication_slots` view on your source database to make sure that this slot doesn't have any active connections. If it does, resolve and close them before proceeding. + 1. Identify the logical replication slot used by an earlier replication task (a parent task) that you want to use as a start point. Then query the `pg_replication_slots` view on your source database to make sure that this slot does not have any active connections. If it does, resolve and close them before proceeding. @@ -394 +394 @@ To enable custom CDC start mode when creating a new CDC-only task using the AWS -When this CDC task runs, AWS DMS raises an error if the specified logical replication slot doesn't exist. It also raises an error if the task isn't created with a valid setting for `cdc-start-position`. +When this CDC task runs, AWS DMS raises an error if the specified logical replication slot does not exist. It also raises an error if the task isn't created with a valid setting for `cdc-start-position`. @@ -477 +477 @@ When performing data type migration, be aware of the following: - * In some cases, the PostgreSQL NUMERIC(p,s) data type doesn't specify any precision and scale. For DMS versions 3.4.2 and earlier, DMS uses a precision of 28 and a scale of 6 by default, NUMERIC(28,6). For example, the value 0.611111104488373 from the source is converted to 0.611111 on the PostgreSQL target. + * In some cases, the PostgreSQL NUMERIC(p,s) data type does not specify any precision and scale. For DMS versions 3.4.2 and earlier, DMS uses a precision of 28 and a scale of 6 by default, NUMERIC(28,6). For example, the value 0.611111104488373 from the source is converted to 0.611111 on the PostgreSQL target. @@ -486 +486 @@ The following table shows source PostgreSQL data types and whether they can be m -Data type | Migrates successfully | Partially migrates | Doesn't migrate | Comments +Data type | Migrates successfully | Partially migrates | does not migrate | Comments @@ -614 +614 @@ The following limitations apply when using a PostgreSQL source endpoint with Bab - * DMS doesn't replicate Babelfish table definition changes to the target endpoint. A workaround for this limitation is to first apply the table definition changes on the target, and then change the table definition on the Babelfish source. + * DMS does not replicate Babelfish table definition changes to the target endpoint. A workaround for this limitation is to first apply the table definition changes on the target, and then change the table definition on the Babelfish source. @@ -618 +618 @@ The following limitations apply when using a PostgreSQL source endpoint with Bab - * DMS doesn't support Full LOB mode for binary data types. Use limited LOB mode for binary data types instead. + * DMS does not support Full LOB mode for binary data types. Use limited LOB mode for binary data types instead. @@ -620 +620 @@ The following limitations apply when using a PostgreSQL source endpoint with Bab - * DMS doesn't support data validation for Babelfish as a source. + * DMS does not support data validation for Babelfish as a source. @@ -626 +626 @@ The following limitations apply when using a PostgreSQL source endpoint with Bab - * DMS doesn't support replication (CDC or Full load and CDC) of partitioned table for Babelfish as a source. + * DMS does not support replication (CDC or Full load and CDC) of partitioned table for Babelfish as a source. @@ -640 +640 @@ To remove the artifacts, issue the following statements (in the order they appea -The event trigger doesn't belong to a specific schema. +The event trigger does not belong to a specific schema. @@ -673 +673 @@ Note that you must set this setting on both the source and target endpoints for -Since MySQL doesn't have a BOOLEAN type, use a transformation rule rather than this setting when migrating BOOLEAN data to MySQL. +Since MySQL does not have a BOOLEAN type, use a transformation rule rather than this setting when migrating BOOLEAN data to MySQL. @@ -707 +707 @@ Only use `MapUnboundedNumericAsString` in PostgreSQL source and target endpoints -`SlotName` | Sets the name of a previously created logical replication slot for a CDC load of the PostgreSQL source instance. When used with the AWS DMS API `CdcStartPosition` request parameter, this attribute also enables using native CDC start points. DMS verifies that the specified logical replication slot exists before starting the CDC load task. It also verifies that the task was created with a valid setting of `CdcStartPosition`. If the specified slot doesn't exist or the task doesn't have a valid `CdcStartPosition` setting, DMS raises an error. For more information about setting the `CdcStartPosition` request parameter, see [Determining a CDC native start point](./CHAP_Task.CDC.html#CHAP_Task.CDC.StartPoint.Native). For more information about using `CdcStartPosition`, see the documentation for the `CreateReplicationTask`, `StartReplicationTask`, and `ModifyReplicationTask` API operations in the [AWS Database Migration Service API Reference](https://docs.aws.amazon.com/dms/latest/APIReference/). Valid values: String Example: `--postgre-sql-settings '{"SlotName": "abc1d2efghijk_34567890_z0yx98w7_6v54_32ut_1srq_1a2b34c5d67ef"}'` +`SlotName` | Sets the name of a previously created logical replication slot for a CDC load of the PostgreSQL source instance. When used with the AWS DMS API `CdcStartPosition` request parameter, this attribute also enables using native CDC start points. DMS verifies that the specified logical replication slot exists before starting the CDC load task. It also verifies that the task was created with a valid setting of `CdcStartPosition`. If the specified slot does not exist or the task does not have a valid `CdcStartPosition` setting, DMS raises an error. For more information about setting the `CdcStartPosition` request parameter, see [Determining a CDC native start point](./CHAP_Task.CDC.html#CHAP_Task.CDC.StartPoint.Native). For more information about using `CdcStartPosition`, see the documentation for the `CreateReplicationTask`, `StartReplicationTask`, and `ModifyReplicationTask` API operations in the [AWS Database Migration Service API Reference](https://docs.aws.amazon.com/dms/latest/APIReference/). Valid values: String Example: `--postgre-sql-settings '{"SlotName": "abc1d2efghijk_34567890_z0yx98w7_6v54_32ut_1srq_1a2b34c5d67ef"}'` @@ -714 +714 @@ The following limitations apply when using PostgreSQL as a source for AWS DMS: - * AWS DMS doesn't work with Amazon RDS for PostgreSQL 10.4 or Amazon Aurora PostgreSQL 10.4 either as source or target. + * AWS DMS does not work with Amazon RDS for PostgreSQL 10.4 or Amazon Aurora PostgreSQL 10.4 either as source or target. @@ -716 +716 @@ The following limitations apply when using PostgreSQL as a source for AWS DMS: - * A captured table must have a primary key. If a table doesn't have a primary key, AWS DMS ignores DELETE and UPDATE record operations for that table. As a workaround, see Enabling change data capture (CDC) using logical replication. + * A captured table must have a primary key. If a table does not have a primary key, AWS DMS ignores DELETE and UPDATE record operations for that table. As a workaround, see Enabling change data capture (CDC) using logical replication. @@ -722 +722 @@ The following limitations apply when using PostgreSQL as a source for AWS DMS: - * AWS DMS doesn't support the **Start Process Changes from Timestamp** run option. + * AWS DMS does not support the **Start Process Changes from Timestamp** run option. @@ -724 +724 @@ The following limitations apply when using PostgreSQL as a source for AWS DMS: - * AWS DMS doesn't replicate changes that result from partition or subpartition operations (`ADD`, `DROP`, or `TRUNCATE`). + * AWS DMS does not replicate changes that result from partition or subpartition operations (`ADD`, `DROP`, or `TRUNCATE`). @@ -726 +726 @@ The following limitations apply when using PostgreSQL as a source for AWS DMS: - * Replication of multiple tables with the same name where each name has a different case (for example, table1, TABLE1, and Table1) can cause unpredictable behavior. Because of this issue, AWS DMS doesn't support this type of replication. + * Replication of multiple tables with the same name where each name has a different case (for example, table1, TABLE1, and Table1) can cause unpredictable behavior. Because of this issue, AWS DMS does not support this type of replication. @@ -728 +728 @@ The following limitations apply when using PostgreSQL as a source for AWS DMS: - * In most cases, AWS DMS supports change processing of CREATE, ALTER, and DROP DDL statements for tables. AWS DMS doesn't support this change processing if the tables are held in an inner function or procedure body block or in other nested constructs. + * In most cases, AWS DMS supports change processing of CREATE, ALTER, and DROP DDL statements for tables. AWS DMS does not support this change processing if the tables are held in an inner function or procedure body block or in other nested constructs. @@ -743 +743 @@ For example, the following change isn't captured. - * AWS DMS doesn't support change processing of TRUNCATE operations. + * AWS DMS does not support change processing of TRUNCATE operations. @@ -751 +751 @@ For example, the following change isn't captured. - * AWS DMS doesn't support change processing to set and unset column default values (using the ALTER COLUMN SET DEFAULT clause on ALTER TABLE statements). + * AWS DMS does not support change processing to set and unset column default values (using the ALTER COLUMN SET DEFAULT clause on ALTER TABLE statements). @@ -753 +753 @@ For example, the following change isn't captured. - * AWS DMS doesn't support change processing to set column nullability (using the ALTER COLUMN [SET|DROP] NOT NULL clause on ALTER TABLE statements). + * AWS DMS does not support change processing to set column nullability (using the ALTER COLUMN [SET|DROP] NOT NULL clause on ALTER TABLE statements). @@ -761 +761 @@ On Aurora PostgreSQL versions 13 and later, you can tune the `logical_decoding_w - * AWS DMS doesn't support replication of partitioned tables. When a partitioned table is detected, the following occurs: + * AWS DMS does not support replication of partitioned tables. When a partitioned table is detected, the following occurs: @@ -775 +775 @@ On Aurora PostgreSQL versions 13 and later, you can tune the `logical_decoding_w - * AWS DMS doesn't support replication of a table with a unique index created with a coalesce function. + * AWS DMS does not support replication of a table with a unique index created with a coalesce function. @@ -781 +781 @@ On Aurora PostgreSQL versions 13 and later, you can tune the `logical_decoding_w - * AWS DMS doesn't support Deferred Constraints. + * AWS DMS does not support Deferred Constraints. @@ -785 +785 @@ On Aurora PostgreSQL versions 13 and later, you can tune the `logical_decoding_w - * AWS DMS doesn't support change processing of two phase commits. + * AWS DMS does not support change processing of two phase commits. @@ -787 +787 @@ On Aurora PostgreSQL versions 13 and later, you can tune the `logical_decoding_w - * AWS DMS doesn't support logical replication to stream long in-progress transactions. + * AWS DMS does not support logical replication to stream long in-progress transactions. @@ -789 +789 @@ On Aurora PostgreSQL versions 13 and later, you can tune the `logical_decoding_w - * AWS DMS doesn't support CDC for Amazon RDS Proxy for PostgreSQL as a source. + * AWS DMS does not support CDC for Amazon RDS Proxy for PostgreSQL as a source. @@ -797 +797 @@ On Aurora PostgreSQL versions 13 and later, you can tune the `logical_decoding_w - * AWS DMS doesn't support CDC for Amazon RDS Multi-AZ database cluster for PostgreSQL as a source, since RDS for PostgreSQL Multi-AZ database clusters don't support logical replication. + * AWS DMS does not support CDC for Amazon RDS Multi-AZ database cluster for PostgreSQL as a source, since RDS for PostgreSQL Multi-AZ database clusters don't support logical replication. @@ -800,0 +801,2 @@ On Aurora PostgreSQL versions 13 and later, you can tune the `logical_decoding_w + * In DDL replication as part of a script, the maximum total number of DDL commands per script is 8192 and maximum total number of lines per script is 8192 lines. +