sharpetronics/PostgreSQL
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-10-18 00:03:40 -04:00
Code Issues Projects Releases Wiki Activity

Fix code indentation vioaltion introduced in commit cc32ec24fd.

Browse Source 
Per buildfarm member koel

Discussion: https://postgr.es/m/CAA4eK1K2Y_iegdXRUNbsghY9+b-4cSOrxYt9T8TtwXkkdWMVJA@mail.gmail.com
This commit is contained in:
Amit Kapila 2023-07-06 11:49:18 +05:30
parent a14354cac0
commit 69a674a170
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/backend/optimizer/plan/planner.c
View File

@ -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 * 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 * 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 * 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 * group locking would cause them to ignore the leader's heavyweight GIN
* GIN page locks would make this unsafe. We'll have to fix that somehow * page locks would make this unsafe. We'll have to fix that somehow if
* if we want to allow parallel inserts in general; updates and deletes * we want to allow parallel inserts in general; updates and deletes have
* have additional problems especially around combo CIDs.) * additional problems especially around combo CIDs.)
* *
* For now, we don't try to use parallel mode if we're running inside a * 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 * parallel worker. We might eventually be able to relax this