AWS prescriptive-guidance documentation change
Summary
Updated documentation about PostgreSQL VACUUM operations: removed 'Rewriting an entire table with VACUUM FULL' from header, improved parameter descriptions, restructured content about vacuum_cost_delay, and adjusted section hierarchy
Security assessment
Changes focus on performance optimization and documentation clarity. No security vulnerabilities, mitigations, or security features are mentioned. The content relates to maintenance best practices rather than security controls.
Diff
diff --git a/prescriptive-guidance/latest/postgresql-maintenance-rds-aurora/manual-vacuum.md b/prescriptive-guidance/latest/postgresql-maintenance-rds-aurora/manual-vacuum.md index a4fba0221..26664efef 100644 --- a//prescriptive-guidance/latest/postgresql-maintenance-rds-aurora/manual-vacuum.md +++ b//prescriptive-guidance/latest/postgresql-maintenance-rds-aurora/manual-vacuum.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Maintenance activities for PostgreSQL databases in Amazon RDS and Amazon Aurora to avoid performance issues](introduction.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Maintenance for PostgreSQL databases in Amazon RDS and Amazon Aurora to avoid performance issues](introduction.html) @@ -7 +7 @@ -Running vacuum and cleanup operations in parallelRewriting an entire table with VACUUM FULL +Running vacuum and cleanup operations in parallel @@ -26 +26,3 @@ We recommend that you run the [VACUUM](https://www.postgresql.org/docs/current/s -To reduce the I/O impact when you run the `VACUUM` and `ANALYZE` commands on concurrent database activity, you can use the `vacuum_cost_delay` parameter. In many situations, maintenance commands such as `VACUUM` and `ANALYZE` don't have to finish quickly. However, these commands shouldn't interfere with the system's ability to perform other database operations. To prevent this, you can enable cost-based vacuum delays by using the `vacuum_cost_delay` parameter. This parameter is disabled by default for manually issued `VACUUM` commands. To enable it, set it to a nonzero value. +To reduce the I/O impact when you run the `VACUUM` and `ANALYZE` commands on concurrent database activity, you can use the `vacuum_cost_delay` parameter. In many situations, maintenance commands such as `VACUUM` and `ANALYZE` don't have to finish quickly. However, these commands shouldn't interfere with the system's ability to perform other database operations. To prevent this, you can enable cost-based vacuum delays by using the `vacuum_cost_delay` parameter. + +This parameter is disabled by default for manually issued `VACUUM` commands. To enable it, set it to a nonzero value. @@ -34 +36 @@ The following parameters help you configure parallel vacuuming in Amazon RDS for - * [max_worker_processes](https://www.postgresql.org/docs/current/runtime-config-resource.html) sets the maximum number of concurrent worker processes. + * [max_worker_processes](https://www.postgresql.org/docs/current/runtime-config-resource.html) – Sets the maximum number of concurrent worker processes. @@ -36 +38 @@ The following parameters help you configure parallel vacuuming in Amazon RDS for - * [min_parallel_index_scan_size](https://www.postgresql.org/docs/current/runtime-config-query.html) sets the minimum amount of index data that must be scanned in order for a parallel scan to be considered. + * [min_parallel_index_scan_size](https://www.postgresql.org/docs/current/runtime-config-query.html) – Sets the minimum amount of index data that must be scanned in order for a parallel scan to be considered. @@ -38 +40 @@ The following parameters help you configure parallel vacuuming in Amazon RDS for - * [max_parallel_maintenance_workers](https://www.postgresql.org/docs/current/runtime-config-resource.html) sets the maximum number of parallel workers that can be started by a single utility command. + * [max_parallel_maintenance_workers](https://www.postgresql.org/docs/current/runtime-config-resource.html) – Sets the maximum number of parallel workers that can be started by a single utility command. @@ -45,3 +47 @@ The following parameters help you configure parallel vacuuming in Amazon RDS for -The `PARALLEL` option is used only for vacuuming purposes. It doesn't affect the `ANALYZE` command. - -The following example illustrates database behavior when you use manual `VACUUM` and `ANALYZE` on a database. +The `PARALLEL` option is used only for vacuuming purposes. It doesn't affect the `ANALYZE` command. The following example illustrates database behavior when you use manual `VACUUM` and `ANALYZE` on a database. @@ -205 +205 @@ Run the `EXPLAIN ANALYZE` command (Plan 4): -If you compare all plan results after you manually analyze the table and collect statistics, you'll notice that the optimizer's Plan 4 is better than the others and also decreases query execution time. This example shows how important it is to run maintenance activities on the database. +If you compare all plan results after you manually analyze the table and collect statistics, you'll notice that the optimizer Plan 4 is better than the others and also decreases query execution time. This example shows how important it is to run maintenance activities on the database. @@ -207 +207 @@ If you compare all plan results after you manually analyze the table and collect -## Rewriting an entire table with VACUUM FULL +### Rewriting an entire table with VACUUM FULL