postgres.git / summary / log / commit / refs

commit    69a674a170058e63e8178aec8a36a673efce8801
Author:   Amit Kapila <akapila@postgresql.org>
Date:     Thu Jul 06 06:19:18 2023 +0000
First released in: 17.0

    Fix code indentation vioaltion introduced in commit cc32ec24fd.
    
    Per buildfarm member koel
    
    Discussion: https://postgr.es/m/CAA4eK1K2Y_iegdXRUNbsghY9+b-4cSOrxYt9T8TtwXkkdWMVJA@mail.gmail.com


 src/backend/optimizer/plan/planner.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/src/backend/optimizer/plan/planner.c b/src/backend/optimizer/plan/planner.c
index 3a4e28b5026..0e12fdeb602 100644
--- a/src/backend/optimizer/plan/planner.c
+++ b/src/backend/optimizer/plan/planner.c
@@ -333,10 +333,10 @@ standard_planner(Query *parse, const char *query_string, int cursorOptions,
 	 * MATERIALIZED VIEW to use parallel plans, but this is safe only because
 	 * the command is writing into a completely new table which workers won't
 	 * be able to see.  If the workers could see the table, the fact that
-	 * group locking would cause them to ignore the leader's heavyweight
-	 * GIN page locks would make this unsafe.  We'll have to fix that somehow
-	 * if we want to allow parallel inserts in general; updates and deletes
-	 * have additional problems especially around combo CIDs.)
+	 * group locking would cause them to ignore the leader's heavyweight GIN
+	 * page locks would make this unsafe.  We'll have to fix that somehow if
+	 * we want to allow parallel inserts in general; updates and deletes have
+	 * additional problems especially around combo CIDs.)
 	 *
 	 * For now, we don't try to use parallel mode if we're running inside a
 	 * parallel worker.  We might eventually be able to relax this


[parent: a14354cac0e3]