AWS prescriptive-guidance documentation change
Summary
Fixed whitespace formatting and alignment in code examples and error messages
Security assessment
The changes consist of non-breaking space removal and code indentation adjustments. No security-related content was added or modified. The error message correction (changing space formatting in 'ERROR: functions...') is purely cosmetic.
Diff
diff --git a/prescriptive-guidance/latest/patterns/migrate-function-based-indexes-from-oracle-to-postgresql.md b/prescriptive-guidance/latest/patterns/migrate-function-based-indexes-from-oracle-to-postgresql.md index 8d13c4ab4..b851276fb 100644 --- a//prescriptive-guidance/latest/patterns/migrate-function-based-indexes-from-oracle-to-postgresql.md +++ b//prescriptive-guidance/latest/patterns/migrate-function-based-indexes-from-oracle-to-postgresql.md @@ -89 +89 @@ Create a function-based index on a column using the to_char function.| Use the f - col1 + col1 @@ -91 +91 @@ Create a function-based index on a column using the to_char function.| Use the f - 2022-08-09 16:00:57.77414 + 2022-08-09 16:00:57.77414 @@ -93 +93 @@ Create a function-based index on a column using the to_char function.| Use the f - + @@ -95 +95 @@ Create a function-based index on a column using the to_char function.| Use the f - ERROR: functions in index expression must be marked IMMUTABLE + ERROR: functions in index expression must be marked IMMUTABLE @@ -155,3 +155,3 @@ If you notice the explain plan, PostgreSQL optimizer has chosen a function-based - LEFT JOIN pg_catalog.pg_namespace n ON n.oid = p.pronamespace - LEFT JOIN pg_catalog.pg_language l ON l.oid = p.prolang - WHERE n.nspname OPERATOR(pg_catalog.~) '^(pg_catalog)$' COLLATE pg_catalog.default AND p.proname='to_char'GROUP BY p.proname,p.provolatile + LEFT JOIN pg_catalog.pg_namespace n ON n.oid = p.pronamespace + LEFT JOIN pg_catalog.pg_language l ON l.oid = p.prolang + WHERE n.nspname OPERATOR(pg_catalog.~) '^(pg_catalog)$' COLLATE pg_catalog.default AND p.proname='to_char'GROUP BY p.proname,p.provolatile @@ -164,2 +164,2 @@ If you notice the explain plan, PostgreSQL optimizer has chosen a function-based - - + + @@ -167 +167 @@ If you notice the explain plan, PostgreSQL optimizer has chosen a function-based - QUERY PLAN + QUERY PLAN @@ -169,2 +169,2 @@ If you notice the explain plan, PostgreSQL optimizer has chosen a function-based - Index Scan using funcindex_idx on funcindex (cost=0.42..8.44 rows=1 width=8) - Index Cond: ((common.to_char(col1, 'DD-MM-YYYY HH24:MI:SS'::character varying))::text = '09-08-2022 16:00:57'::text) + Index Scan using funcindex_idx on funcindex (cost=0.42..8.44 rows=1 width=8) + Index Cond: ((common.to_char(col1, 'DD-MM-YYYY HH24:MI:SS'::character varying))::text = '09-08-2022 16:00:57'::text)