Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit69a674a

Browse files
author
Amit Kapila
committed
Fix code indentation vioaltion introduced in commitcc32ec2.
Per buildfarm member koelDiscussion:https://postgr.es/m/CAA4eK1K2Y_iegdXRUNbsghY9+b-4cSOrxYt9T8TtwXkkdWMVJA@mail.gmail.com
1 parenta14354c commit69a674a

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

‎src/backend/optimizer/plan/planner.c

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -333,10 +333,10 @@ standard_planner(Query *parse, const char *query_string, int cursorOptions,
333333
* MATERIALIZED VIEW to use parallel plans, but this is safe only because
334334
* the command is writing into a completely new table which workers won't
335335
* be able to see. If the workers could see the table, the fact that
336-
* group locking would cause them to ignore the leader's heavyweight
337-
*GINpage locks would make this unsafe. We'll have to fix that somehow
338-
*ifwe want to allow parallel inserts in general; updates and deletes
339-
*haveadditional problems especially around combo CIDs.)
336+
* group locking would cause them to ignore the leader's heavyweight GIN
337+
* page locks would make this unsafe. We'll have to fix that somehow if
338+
* we want to allow parallel inserts in general; updates and deletes have
339+
* additional problems especially around combo CIDs.)
340340
*
341341
* For now, we don't try to use parallel mode if we're running inside a
342342
* parallel worker. We might eventually be able to relax this

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp