Modified recipe in 20170209 to remove comment

diff --git a/update_releases/current/20170209updaterelease.md b/update_releases/current/20170209updaterelease.md
index 54686a356549d96a829db4de497c54889424f9b0..c68ee3515ad2d369a0fe45b7ed8adc9168630680 100644 (file)
--- a/update_releases/current/20170209updaterelease.md
+++ b/update_releases/current/20170209updaterelease.md
@@ -75,7 +75,6 @@ If you believe you have been affected by the aforementioned CREATE INDEX CONCURR
 
     CREATE INDEX CONCURRENTLY new_index_name ON table_name (column_name);
     DROP INDEX CONCURRENTLY old_index_name;
-    /* if you wish, you can rename your index to match the old index name */
     ALTER INDEX new_index_name RENAME TO old_index_name;
 
 Note that using this method means you will briefly have two copies of the same index, so if disk space is an issue you may need to take other approaches.

diff --git a/update_releases/current/20170209updaterelease.txt b/update_releases/current/20170209updaterelease.txt
index f7d5fe69cfbcb1ae195c8ab60f5a52e5ff98a66e..59266151fc0b18a4932c35245375a6034c6836e6 100644 (file)
--- a/update_releases/current/20170209updaterelease.txt
+++ b/update_releases/current/20170209updaterelease.txt
@@ -75,7 +75,6 @@ If you believe you have been affected by the aforementioned CREATE INDEX CONCURR
 
     CREATE INDEX CONCURRENTLY new_index_name ON table_name (column_name);
     DROP INDEX CONCURRENTLY old_index_name;
-    /* if you wish, you can rename your index to match the old index name */
     ALTER INDEX new_index_name RENAME TO old_index_name;
 
 Note that using this method means you will briefly have two copies of the same index, so if disk space is an issue you may need to take other approaches.