Invent min_parallel_relation_size GUC to replace a hard-wired constant.
The main point of doing this is to allow the cutoff to be set very small, even zero, to allow parallel-query behavior to be tested on relatively small tables such as we typically use in the regression tests. But it might be of use to users too. The number-of-workers scaling behavior in create_plain_partial_paths() is pretty ad-hoc and subject to change, so we won't expose anything about that, but the notion of not considering parallel query at all for tables below size X seems reasonably stable. Amit Kapila, per a suggestion from me Discussion: <17170.1465830165@sss.pgh.pa.us>
Showing
- doc/src/sgml/config.sgml 14 additions, 0 deletionsdoc/src/sgml/config.sgml
- src/backend/optimizer/path/allpaths.c 10 additions, 5 deletionssrc/backend/optimizer/path/allpaths.c
- src/backend/utils/misc/guc.c 11 additions, 0 deletionssrc/backend/utils/misc/guc.c
- src/backend/utils/misc/postgresql.conf.sample 1 addition, 0 deletionssrc/backend/utils/misc/postgresql.conf.sample
- src/include/optimizer/paths.h 1 addition, 0 deletionssrc/include/optimizer/paths.h
Loading
Please register or sign in to comment