AWS prescriptive-guidance documentation change
Summary
Merged two paragraphs about PostgreSQL logical replication publications and replica identity into a single paragraph, removing a blank line. No content change.
Security assessment
The change is purely a formatting adjustment. The content remains the same and discusses replication mechanics without any security context. There is no evidence of addressing vulnerabilities or adding security features.
Diff
diff --git a/prescriptive-guidance/latest/migration-databases-postgresql-ec2/logical-replication-considerations.md b/prescriptive-guidance/latest/migration-databases-postgresql-ec2/logical-replication-considerations.md index b2a4c34eb..0eba6432f 100644 --- a//prescriptive-guidance/latest/migration-databases-postgresql-ec2/logical-replication-considerations.md +++ b//prescriptive-guidance/latest/migration-databases-postgresql-ec2/logical-replication-considerations.md @@ -35,3 +35 @@ The following workflow steps show how a logical replication architecture works: -A _publication_ can be defined on a primary instance (publisher). A publication is a set of changes generated from a table or a group of tables. You can choose changes from a combination of INSERT, UPDATE, DELETE, and TRUNCATE operations. By default, all these changes are replicated to the subscriber database. This is in contrast with physical replication, where exact block addresses are used for a byte-by-byte replication. - -A published table must have a [REPLICA IDENTITY](https://www.postgresql.org/docs/current/sql-altertable.html#SQL-ALTERTABLE-REPLICA-IDENTITY) configured to replicate UPDATE and DELETE operations so that appropriate rows to update or delete can be identified on the subscriber side. In most cases, the replica identity is determined by either a primary key or unique key. If a primary key is not present and you can't create one, then you can set the replica identity to `full`. This means the entire row becomes the key. We recommend that you set the replica identity to `full` as a last resort because this setting is inefficient. +A _publication_ can be defined on a primary instance (publisher). A publication is a set of changes generated from a table or a group of tables. You can choose changes from a combination of INSERT, UPDATE, DELETE, and TRUNCATE operations. By default, all these changes are replicated to the subscriber database. This is in contrast with physical replication, where exact block addresses are used for a byte-by-byte replication. A published table must have a [REPLICA IDENTITY](https://www.postgresql.org/docs/current/sql-altertable.html#SQL-ALTERTABLE-REPLICA-IDENTITY) configured to replicate UPDATE and DELETE operations so that appropriate rows to update or delete can be identified on the subscriber side. In most cases, the replica identity is determined by either a primary key or unique key. If a primary key is not present and you can't create one, then you can set the replica identity to `full`. This means the entire row becomes the key. We recommend that you set the replica identity to `full` as a last resort because this setting is inefficient.