Skip to content

G
Gpdb

Greenplum / Gpdb

通知 7
Star 1
Fork 0
G
Gpdb

前往新版Gitcode，体验更适合开发者的 AI 搜索 >>

切换分支/标签
查找文件 普通视图历史永久链接Permalink
guc-list.xml 398.7 KB
Newer Older
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
1 2 3 4 5 6 7 8 
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE topic
  PUBLIC "-//OASIS//DTD DITA Composite//EN" "ditabase.dtd">
<topic id="topic3">
  <title>Configuration Parameters</title>
  <abstract>Descriptions of the Greenplum Database server configuration parameters listed
    alphabetically.</abstract>
  <body>
D
Docs - making guc table print-only instead of html to avoid formatting problems  
dyozie 已提交
9 
    <!--Table is PDF only-->
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
10 
    <simpletable frame="all" relcolwidth="1.0* 1.09* 1.13*" id="simpletable_c53_rlx_wp"
D
Docs - making guc table print-only instead of html to avoid formatting problems  
dyozie 已提交
11 
      otherprops="op-print">
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 
      <strow>
        <stentry>
          <ul id="ul_tc3_nlx_wp">
            <li>
              <xref href="#application_name"/>
            </li>
            <li>
              <xref href="#array_nulls"/>
            </li>
            <li>
              <xref href="#authentication_timeout"/>
            </li>
            <li>
              <xref href="#backslash_quote"/>
            </li>
            <li>
              <xref href="#block_size"/>
            </li>
            <li>
              <xref href="#bonjour_name"/>
            </li>
            <li>
              <xref href="#check_function_bodies"/>
            </li>
            <li>
              <xref href="#client_encoding"/>
            </li>
            <li>
              <xref href="#client_min_messages"/>
            </li>
            <li>
              <xref href="#cpu_index_tuple_cost"/>
            </li>
            <li>
              <xref href="#cpu_operator_cost"/>
            </li>
            <li>
              <xref href="#cpu_tuple_cost"/>
            </li>
            <li>
              <xref href="#cursor_tuple_fraction"/>
            </li>
C
Add ignore_checksum_failure GUC to reference (#2933)  
Chuck Litzell 已提交
54 
            <li><xref href="#data_checksums" format="dita"/></li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 
            <li>
              <xref href="#DateStyle"/>
            </li>
            <li>
              <xref href="#db_user_namespace"/>
            </li>
            <li>
              <xref href="#deadlock_timeout"/>
            </li>
            <li>
              <xref href="#debug_assertions"/>
            </li>
            <li>
              <xref href="#debug_pretty_print"/>
            </li>
            <li>
              <xref href="#debug_print_parse"/>
            </li>
            <li>
              <xref href="#debug_print_plan"/>
            </li>
            <li>
              <xref href="#debug_print_prelim_plan"/>
            </li>
            <li>
              <xref href="#debug_print_rewritten"/>
            </li>
            <li>
              <xref href="#debug_print_slice_table"/>
            </li>
            <li>
              <xref href="#default_statistics_target"/>
            </li>
            <li>
              <xref href="#default_tablespace"/>
            </li>
C
Adds PostgreSQL full text search docs to GPDB docs (#6013)  
Chuck Litzell 已提交
91 
            <li><xref href="#default_text_search_config" format="dita"/></li>
D
Docs postgresql 9.1 merge (#6979)  
David Yozie 已提交
92 
            <li>
M
docs - minor fixes to GUC list  
mkiyama 已提交
93 
              <xref href="#default_transaction_deferrable"/>
D
Docs postgresql 9.1 merge (#6979)  
David Yozie 已提交
94 
            </li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 
            <li>
              <xref href="#default_transaction_isolation"/>
            </li>
            <li>
              <xref href="#default_transaction_read_only"/>
            </li>
            <li>
              <xref href="#dynamic_library_path"/>
            </li>
            <li>
              <xref href="#effective_cache_size"/>
            </li>
            <li>
              <xref href="#enable_bitmapscan"/>
            </li>
            <li>
              <xref href="#enable_groupagg"/>
            </li>
            <li>
              <xref href="#enable_hashagg"/>
            </li>
            <li>
              <xref href="#enable_hashjoin"/>
            </li>
            <li>
              <xref href="#enable_indexscan"/>
            </li>
            <li>
              <xref href="#enable_mergejoin"/>
            </li>
            <li>
              <xref href="#enable_nestloop"/>
            </li>
            <li>
              <xref href="#enable_seqscan"/>
            </li>
            <li>
              <xref href="#enable_sort"/>
            </li>
            <li>
              <xref href="#enable_tidscan"/>
            </li>
            <li>
              <xref href="#escape_string_warning"/>
            </li>
            <li>
              <xref href="#explain_pretty_print"/>
            </li>
            <li>
              <xref href="#extra_float_digits"/>
            </li>
            <li>
              <xref href="#from_collapse_limit"/>
            </li>
            <li>
              <xref href="#gp_adjust_selectivity_for_outerjoins"/>
            </li>
            <li>
              <xref href="#gp_appendonly_compaction"/>
            </li>
            <li>
              <xref href="#gp_appendonly_compaction_threshold"/>
            </li>
            <li>
              <xref href="#gp_autostats_mode"/>
            </li>
            <li>
              <xref href="#gp_autostats_mode_in_functions" type="section"
                >gp_autostats_mode_in_functions</xref>
            </li>
            <li>
              <xref href="#gp_autostats_on_change_threshold"/>
            </li>
            <li>
              <xref href="#gp_cached_segworkers_threshold"/>
            </li>
            <li>
              <xref href="#gp_command_count"/>
            </li>
            <li>
              <xref href="#gp_connection_send_timeout"/>
            </li>
            <li>
              <xref href="#gp_content"/>
            </li>
            <li>
              <xref href="#gp_create_table_random_default_distribution"/>
            </li>
            <li>
              <xref href="#gp_dbid"/>
            </li>
            <li>
              <xref href="#gp_debug_linger"/>
            </li>
            <li>
              <xref href="#gp_default_storage_options"/>
            </li>
            <li>
              <xref href="#gp_dynamic_partition_pruning"/>
            </li>
            <li>
              <xref href="#gp_enable_agg_distinct"/>
            </li>
            <li>
              <xref href="#gp_enable_agg_distinct_pruning"/>
            </li>
            <li>
              <xref href="#gp_enable_direct_dispatch"/>
            </li>
            <li>
              <xref href="#gp_enable_exchange_default_partition"
                >gp_enable_exchange_default_partition</xref>
            </li>
            <li>
              <xref href="#gp_enable_fast_sri"/>
            </li>
M
docs - add GUC gp_enable_global_deadlock_detector (#6894)  
Mel Kiyama 已提交
211 
            <li><xref href="#gp_enable_global_deadlock_detector"/></li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 
            <li>
              <xref href="#gp_enable_gpperfmon"/>
            </li>
            <li>
              <xref href="#gp_enable_groupext_distinct_gather"/>
            </li>
            <li>
              <xref href="#gp_enable_groupext_distinct_pruning"/>
            </li>
            <li>
              <xref href="#gp_enable_multiphase_agg"/>
            </li>
            <li>
              <xref href="#gp_enable_predicate_propagation"/>
            </li>
            <li>
              <xref href="#gp_enable_preunique"/>
            </li>
C
docs: add real-time query metrics GUCs to reference (#4618)  
Chuck Litzell 已提交
230 231 232 
            <li>
              <xref href="#gp_enable_query_metrics"/>
            </li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
233 234 
            <li>
              <xref href="#gp_enable_relsize_collection" format="dita"/></li>
M
DOCS: New GUC gp_enable_segment_copy_checking. COPY ON SEGMENT changes (#3046)  
Mel Kiyama 已提交
235 236 
            <li>
              <xref href="#gp_enable_segment_copy_checking" format="dita"/></li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
237 238 239 240 241 242 243 244 245 246 247 248 
            <li>
              <xref href="#gp_enable_sort_distinct"/>
            </li>
            <li>
              <xref href="#gp_enable_sort_limit"/>
            </li>
            <li>
              <xref href="#gp_external_enable_exec"/>
            </li>
            <li>
              <xref href="#gp_external_max_segs"/>
            </li>
I
Implement filter pushdown for PXF data sources (#4968)  
Ivan Leskin 已提交
249 250 251 
            <li>
              <xref href="#gp_external_enable_filter_pushdown"/>
            </li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
252 253 254 255 256 257 258 259 260 261 262 263 
            <li>
              <xref href="#gp_fts_probe_interval"/>
            </li>
            <li>
              <xref href="#gp_fts_probe_retries"/>
            </li>
            <li>
              <xref href="#gp_fts_probe_threadcount"/>
            </li>
            <li>
              <xref href="#gp_fts_probe_timeout"/>
            </li>
L
docs - discuss the global deadlock detector (#6538)  
Lisa Owen 已提交
264 265 266 
            <li>
              <xref href="#gp_global_deadlock_detector_period"/>
            </li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
267 268 269 270 
            <li>
              <xref href="#gp_gpperfmon_send_interval"/>
            </li>
            <li>
M
docs - minor fixes to GUC list  
mkiyama 已提交
271 
              <xref href="#gp_hashjoin_tuples_per_bucket"/>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
272 
            </li>
M
docs - add gp_resource_groups, gp_use_legacy_hashops to GUC table.  
mkiyama 已提交
273 274 275 276 277 
            <li>
              <xref href="#gp_resource_manager"/>
            </li>
            <li>
              <xref href="#gp_use_legacy_hashops"/></li>
M
docs - minor fixes to GUC list  
mkiyama 已提交
278 
            <li><xref href="#gp_vmem_idle_resource_timeout"/></li>
M
docs - add gp_workfile_* GUCs to GUC table  
mkiyama 已提交
279 280 281 282 283 284 
            <li><xref href="#gp_vmem_protect_limit"/></li>
            <li><xref href="#gp_vmem_protect_segworker_cache_limit"/></li>
            <li><xref href="#gp_workfile_compression"/></li>
            <li><xref href="#gp_workfile_limit_files_per_query"/></li>
            <li><xref href="#gp_workfile_limit_per_query"/></li>
            <li><xref href="#gp_workfile_limit_per_segment"/></li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
285 
            <li>
M
docs - minor fixes to GUC list  
mkiyama 已提交
286 
              <xref href="#gpperfmon_log_alert_level"/>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
287 288 289 290 
            </li>
            <li>
              <xref href="#gpperfmon_port"/>
            </li>
C
Add ignore_checksum_failure GUC to reference (#2933)  
Chuck Litzell 已提交
291 
            <li><xref href="#ignore_checksum_failure" format="dita"/></li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 
            <li>
              <xref href="#integer_datetimes"/>
            </li>
            <li>
              <xref href="#IntervalStyle"/>
            </li>
            <li>
              <xref href="#join_collapse_limit"/>
            </li>
            <li>
              <xref href="#keep_wal_segments"/>
            </li>
            <li>
              <xref href="#krb_caseins_users"/>
            </li>
            <li>
              <xref href="#krb_server_keyfile"/>
            </li>
            <li>
              <xref href="#lc_collate"/>
            </li>
            <li>
              <xref href="#lc_ctype"/>
            </li>
            <li>
              <xref href="#lc_messages"/>
            </li>
            <li>
              <xref href="#lc_monetary"/>
            </li>
            <li>
              <xref href="#lc_numeric"/>
            </li>
            <li>
              <xref href="#lc_time"/>
            </li>
D
Docs - moving guc list table to 2-column format to adhere to style  
David Yozie 已提交
328 329 330 331 
          </ul>
        </stentry>
        <stentry>
          <ul id="ul_wwy_bmx_wp">
M
docs - add gp_workfile_* GUCs to GUC table  
mkiyama 已提交
332 333 334 
            <li>
              <xref href="#listen_addresses"/>
            </li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 
            <li>
              <xref href="#log_planner_stats"/>
            </li>
            <li>
              <xref href="#log_rotation_age"/>
            </li>
            <li>
              <xref href="#log_rotation_size"/>
            </li>
            <li>
              <xref href="#log_statement"/>
            </li>
            <li>
              <xref href="#log_statement_stats"/>
            </li>
J
Add doc for log_temp_files (#2969)  
Jane Beckman 已提交
350 351 352 
            <li>
              <xref href="#log_temp_files"/>
            </li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
353 354 355 356 357 358 
            <li>
              <xref href="#log_timezone"/>
            </li>
            <li>
              <xref href="#log_truncate_on_rotation"/>
            </li>
D
adding reference topic for maintenance_work_mem, which is mentioned elsewhere...  
David Yozie 已提交
359 
            <li><xref href="#maintenance_work_mem" format="dita"/></li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 
            <li>
              <xref href="#max_appendonly_tables"/>
            </li>
            <li>
              <xref href="#max_connections"/>
            </li>
            <li>
              <xref href="#max_files_per_process"/>
            </li>
            <li>
              <xref href="#max_function_args"/>
            </li>
            <li>
              <xref href="#max_identifier_length"/>
            </li>
            <li>
              <xref href="#max_index_keys"/>
            </li>
            <li>
              <xref href="#max_locks_per_transaction"/>
            </li>
            <li>
              <xref href="#max_prepared_transactions"/>
            </li>
            <li>
              <xref href="#max_resource_portals_per_transaction"/>
            </li>
            <li>
              <xref href="#max_resource_queues"/>
            </li>
            <li>
              <xref href="#max_stack_depth"/>
            </li>
            <li>
              <xref href="#max_statement_mem"/>
            </li>
L
docs - memory_spill_ratio guc and related content (#3278)  
Lisa Owen 已提交
396 397 398 
            <li>
              <xref href="#memory_spill_ratio"/>
            </li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
399 400 401 402 403 404 405 406 407 408 409 410 
            <li>
              <xref href="#optimizer" type="section">optimizer</xref>
            </li>
            <li><xref href="#optimizer_array_expansion_threshold" type="section"
                >optimizer_array_expansion_threshold</xref></li>
            <li>
              <xref href="#optimizer_analyze_root_partition" type="section"
                >optimizer_analyze_root_partition</xref>
            </li>
            <li>
              <xref href="#optimizer_control" type="section">optimizer_control</xref>
            </li>
M
GPDB DOCS - new GUCs from 4.3.x and mdcache (#2518)  
mkiyama 已提交
411 412 413 414 
            <li>
              <xref href="#optimizer_cte_inlining_bound" type="section"
                >optimizer_cte_inlining_bound</xref>
            </li>
M
docs: gporca updates (#4792)  
Mel Kiyama 已提交
415 416 417 
            <li><xref href="#optimizer_enable_associativity" type="section"
                >optimizer_enable_associativity</xref>
            </li>
M
docs - add GUC optimizer_enable_dml (#8725)  
Mel Kiyama 已提交
418 419 
            <li><xref href="#optimizer_enable_dml" type="section">optimizer_enable_dml</xref>
            </li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
420 421 422 423 
            <li>
              <xref href="#optimizer_enable_master_only_queries" type="section"
                >optimizer_enable_master_only_queries</xref>
            </li>
M
docs - new GUC optimizer_enable_agg_skew_avoidance (#6547)  
Mel Kiyama 已提交
424 425 426 
            <li><xref href="#optimizer_force_agg_skew_avoidance" type="section"
                >optimizer_force_agg_skew_avoidance</xref>
            </li>
M
GPDB DOCS - new GUCs from 4.3.x and mdcache (#2518)  
mkiyama 已提交
427 428 429 430 431 432 433 434 
            <li>
              <xref href="#optimizer_force_multistage_agg" type="section"
                >optimizer_force_multistage_agg</xref>
            </li>
            <li>
              <xref href="#optimizer_force_three_stage_scalar_dqa" type="section"
                >optimizer_force_three_stage_scalar_dqa</xref>
            </li>
M
docs: add orca guc optimizer_join_arity_for_associativity_commutativity (#3520)  
Mel Kiyama 已提交
435 436 437 
            <li><xref href="#optimizer_join_arity_for_associativity_commutativity" type="section"
                >optimizer_join_arity_for_associativity_commutativity</xref>
            </li>
C
docs: optimizer_join_order guc (#4014)  
Chuck Litzell 已提交
438 439 440 
            <li>
              <xref href="#optimizer_join_order" type="section">optimizer_join_order</xref>
            </li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
441 442 443 444 
            <li>
              <xref href="#optimizer_join_order_threshold" type="section"
                >optimizer_join_order_threshold</xref>
            </li>
M
GPDB DOCS - new GUCs from 4.3.x and mdcache (#2518)  
mkiyama 已提交
445 446 447 448 449 450 
            <li>
              <xref href="#optimizer_mdcache_size" type="section"/>
            </li>
            <li>
              <xref href="#optimizer_metadata_caching" type="section"/>
            </li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
451 452 453 
            <li>
              <xref href="#optimizer_minidump" type="section">optimizer_minidump</xref>
            </li>
M
GPDB DOCS - new GUCs from 4.3.x and mdcache (#2518)  
mkiyama 已提交
454 455 456 457 
            <li>
              <xref href="#optimizer_nestloop_factor" type="section"
                >optimizer_nestloop_factor</xref>
            </li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
458 459 460 
            <li>
              <xref href="#optimizer_parallel_union" type="section"
              >optimizer_parallel_union</xref></li>
M
docs - fix GUC name optimizer_penalize_skewed_hashjoin -> optimizer_penalize_skew  
mkiyama 已提交
461 462 
            <li><xref href="#optimizer_penalize_skew" type="section"
              >optimizer_penalize_skew</xref></li>
M
GPDB DOCS - new GUCs from 4.3.x and mdcache (#2518)  
mkiyama 已提交
463 464 465 466 467 468 469 470 
            <li>
              <xref href="#optimizer_print_missing_stats" type="section"
                >optimizer_print_missing_stats</xref>
            </li>
            <li>
              <xref href="#optimizer_print_optimization_stats" type="section"
                >optimizer_print_optimization_stats</xref>
            </li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
471 472 
            <li>
              <xref href="#optimizer_sort_factor" format="dita">optimizer_sort_factor</xref></li>
M
docs - add guc optimizer_use_gpdb_allocators (#8767)  
Mel Kiyama 已提交
473 474 475 
            <li>
              <xref href="#optimizer_use_gpdb_allocators" format="dita"
                >optimizer_use_gpdb_allocators</xref></li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 
            <li>
              <xref href="#password_encryption"/>
            </li>
            <li>
              <xref href="#password_hash_algorithm"/>
            </li>
            <li>
              <xref href="#pljava_classpath"/>
            </li>
            <li>
              <xref href="#pljava_classpath_insecure"/>
            </li>
            <li>
              <xref href="#pljava_statement_cache_size"/>
            </li>
            <li>
              <xref href="#pljava_release_lingering_savepoints"/>
            </li>
            <li>
              <xref href="#pljava_vmoptions"/>
            </li>
            <li>
              <xref href="#port"/>
            </li>
            <li>
              <xref href="#random_page_cost"/>
            </li>
            <li>
              <xref href="#readable_external_table_timeout"/>
            </li>
            <li>
              <xref href="#repl_catchup_within_range"/>
            </li>
            <li>
              <xref href="#replication_timeout"/>
            </li>
            <li>
              <xref href="#regex_flavor"/>
            </li>
            <li>
              <xref href="#resource_cleanup_gangs_on_wait"/>
            </li>
            <li>
              <xref href="#resource_select_only"/>
            </li>
            <li>
              <xref href="#runaway_detector_activation_percent"/>
            </li>
            <li>
              <xref href="#search_path"/>
            </li>
            <li>
              <xref href="#seq_page_cost"/>
            </li>
            <li>
              <xref href="#server_encoding"/>
            </li>
            <li>
              <xref href="#server_version"/>
            </li>
            <li>
              <xref href="#server_version_num"/>
            </li>
            <li>
              <xref href="#shared_buffers"/>
            </li>
            <li>
              <xref href="#shared_preload_libraries"/>
            </li>
            <li>
              <xref href="#ssl"/>
            </li>
            <li>
              <xref href="#ssl_ciphers"/>
            </li>
            <li>
              <xref href="#standard_conforming_strings"/>
            </li>
            <li>
              <xref href="#statement_mem"/>
            </li>
            <li>
              <xref href="#statement_timeout"/>
            </li>
            <li>
              <xref href="#stats_queue_level"/>
            </li>
            <li>
D
Adding reference topic and additional docs around temp_tablespaces (#8025)  
David Yozie 已提交
564 
              <xref href="#superuser_reserved_connections"/></li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
565 566 567 568 569 570 571 572 573 574 575 576 
            <li>
              <xref href="#tcp_keepalives_count"/>
            </li>
            <li>
              <xref href="#tcp_keepalives_idle"/>
            </li>
            <li>
              <xref href="#tcp_keepalives_interval"/>
            </li>
            <li>
              <xref href="#temp_buffers"/>
            </li>
D
Adding reference topic and additional docs around temp_tablespaces (#8025)  
David Yozie 已提交
577 578 
            <li><xref href="#topic_k52_fqm_f3b" format="dita"/>
            </li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
579 580 581 582 583 584 
            <li>
              <xref href="#TimeZone"/>
            </li>
            <li>
              <xref href="#timezone_abbreviations"/>
            </li>
H
Clean up max, flags, and docs of 'track_activity_query_size' setting.  
Heikki Linnakangas 已提交
585 586 587 
            <li>
              <xref href="#track_activity_query_size"/>
            </li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 
            <li>
              <xref href="#transaction_isolation"/>
            </li>
            <li>
              <xref href="#transaction_read_only"/>
            </li>
            <li>
              <xref href="#transform_null_equals"/>
            </li>
            <li>
              <xref href="#unix_socket_directory"/>
            </li>
            <li>
              <xref href="#unix_socket_group"/>
            </li>
            <li>
              <xref href="#unix_socket_permissions"/>
            </li>
            <li>
              <xref href="#update_process_title"/>
            </li>
            <li>
              <xref href="#vacuum_cost_delay"/>
            </li>
            <li>
              <xref href="#vacuum_cost_limit"/>
            </li>
            <li>
              <xref href="#vacuum_cost_page_dirty"/>
            </li>
            <li>
              <xref href="#vacuum_cost_page_hit"/>
            </li>
            <li>
              <xref href="#vacuum_cost_page_miss"/>
            </li>
            <li>
              <xref href="#vacuum_freeze_min_age"/>
            </li>
            <li>
              <xref href="#validate_previous_free_tid"/>
            </li>
M
docs: Add guc verify_gpfdists_cert (#4851)  
Mel Kiyama 已提交
630 
            <li><xref href="#verify_gpfdists_cert"/></li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
631 632 633 634 635 636 
            <li><xref href="#vmem_process_interrupt" type="section"
              >vmem_process_interrupt</xref></li>
            <li>
              <xref href="#wal_receiver_status_interval"/>
            </li>
            <li><xref href="#writable_external_table_bufsize" type="section"
I
Implement filter pushdown for PXF data sources (#4968)  
Ivan Leskin 已提交
637 638 
                >writable_external_table_bufsize</xref>
            </li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
639 640 641 642 643 644 
            <li>
              <xref href="#xid_stop_limit"/>
            </li>
            <li>
              <xref href="#xid_warn_limit"/>
            </li>
M
GPDB DOCS - XML gucs xmlbinary, xmloption (#2304)  
mkiyama 已提交
645 646 647 648 
            <li><xref href="#xmlbinary"/>
            </li>
            <li><xref href="#xmloption"/>
            </li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 
          </ul>
        </stentry>
      </strow>
    </simpletable>
  </body>
  <topic id="application_name">
    <title>application_name</title>
    <body>
      <p>Sets the application name for a client session. For example, if connecting via
          <codeph>psql</codeph>, this will be set to <codeph>psql</codeph>. Setting an application
        name allows it to be reported in log messages and statistics views.</p>
      <table id="application_name_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">string</entry>
              <entry colname="col2"/>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="array_nulls">
    <title>array_nulls</title>
    <body>
      <p>This controls whether the array input parser recognizes unquoted NULL as specifying a null
        array element. By default, this is on, allowing array values containing null values to be
        entered. <ph>Greenplum Database versions before 3.0 did not support null values in arrays,
          and therefore would treat NULL as specifying a normal array element with the string value
          'NULL'.</ph></p>
      <table id="array_nulls_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="authentication_timeout">
    <title>authentication_timeout</title>
    <body>
      <p>Maximum time to complete client authentication. This prevents hung clients from occupying a
        connection indefinitely.</p>
      <table id="authentication_timeout_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Any valid time expression (number and unit)</entry>
              <entry colname="col2">1min</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="backslash_quote">
    <title>backslash_quote</title>
    <body>
      <p>This controls whether a quote mark can be represented by \' in a string literal. The
        preferred, SQL-standard way to represent a quote mark is by doubling it ('') but PostgreSQL
        has historically also accepted \'. However, use of \' creates security risks because in some
        client character set encodings, there are multibyte characters in which the last byte is
        numerically equivalent to ASCII \.</p>
      <table id="backslash_quote_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">on (allow \' always)<p>off (reject always)</p><p>safe_encoding
                  (allow only if client encoding does not allow ASCII \ within a multibyte
                  character)</p></entry>
              <entry colname="col2">safe_encoding</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="block_size">
    <title>block_size</title>
    <body>
      <p>Reports the size of a disk block.</p>
      <table id="block_size_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">number of bytes</entry>
              <entry colname="col2">32768</entry>
              <entry colname="col3">read only</entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="bonjour_name">
    <title>bonjour_name</title>
    <body>
      <p>Specifies the Bonjour broadcast name. By default, the computer name is used, specified as
        an empty string. This option is ignored if the server was not compiled with Bonjour
        support.</p>
      <table id="bonjour_name_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">string</entry>
              <entry colname="col2">unset</entry>
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="check_function_bodies">
    <title>check_function_bodies</title>
    <body>
      <p>When set to off, disables validation of the function body string during <codeph>CREATE
          FUNCTION</codeph>. Disabling validation is occasionally useful to avoid problems such as
        forward references when restoring function definitions from a dump.</p>
      <table id="check_function_bodies_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="client_encoding">
    <title>client_encoding</title>
    <body>
      <p>Sets the client-side encoding (character set). The default is to use the same as the
        database encoding. See <xref
D
Docs: Updating postgresql.org references to 9.4  
David Yozie 已提交
865 
          href="https://www.postgresql.org/docs/9.4/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED"
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 
          scope="external" format="html">Supported Character Sets</xref> in the PostgreSQL
        documentation.</p>
      <table id="client_encoding_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">character set</entry>
              <entry colname="col2">UTF8</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="client_min_messages">
    <title>client_min_messages</title>
    <body>
      <p>Controls which message levels are sent to the client. Each level includes all the levels
        that follow it. The later the level, the fewer messages are sent.</p>
      <table id="client_min_messages_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">DEBUG5
M
docs: COPY command - add PROGRAM clause (#3297)  
Mel Kiyama 已提交
911 
                  <p>DEBUG4</p><p>DEBUG3</p><p>DEBUG2</p><p>DEBUG1</p><p>LOG</p><p>NOTICE</p><p>WARNING</p><p>ERROR</p><p>FATAL</p><p>PANIC</p></entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
912 913 914 915 916 917 
              <entry colname="col2">NOTICE</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
L
docs - doc updates for recent 9.4 merges (#8553)  
Lisa Owen 已提交
918 
      <p><codeph>INFO</codeph> level messages are always sent to the client.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
919 920 921 922 923 
    </body>
  </topic>
  <topic id="cpu_index_tuple_cost">
    <title>cpu_index_tuple_cost</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
924 
      <p>For the Postgres Planner, sets the estimate of the cost of processing each
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 
        index row during an index scan. This is measured as a fraction of the cost of a sequential
        page fetch.</p>
      <table id="cpu_index_tuple_cost_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">floating point</entry>
              <entry colname="col2">0.005</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="cpu_operator_cost">
    <title>cpu_operator_cost</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
953 
      <p>For the Postgres Planner, sets the estimate of the cost of processing each
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 
        operator in a WHERE clause. This is measured as a fraction of the cost of a sequential page
        fetch. </p>
      <table id="cpu_operator_cost_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">floating point</entry>
              <entry colname="col2">0.0025</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="cpu_tuple_cost">
    <title>cpu_tuple_cost</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
982 
      <p>For the Postgres Planner, Sets the estimate of the cost of processing each
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 
        row during a query. This is measured as a fraction of the cost of a sequential page
        fetch.</p>
      <table id="cpu_tuple_cost_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">floating point</entry>
              <entry colname="col2">0.01</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="cursor_tuple_fraction">
    <title>cursor_tuple_fraction</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
1011 1012 
      <p>Tells the Postgres Planner how many rows are expected to be fetched in a
        cursor query, thereby allowing the Postgres Planner to use this information to optimize the
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 
        query plan. The default of 1 means all rows will be fetched. </p>
      <table id="cursor_tuple_fraction_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
              <entry colname="col2">1</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
C
Add ignore_checksum_failure GUC to reference (#2933)  
Chuck Litzell 已提交
1037 
  <topic id="data_checksums">
C
Add heap checksums to gpinitsystem ref and GUC reference (#2915)  
Chuck Litzell 已提交
1038 1039 
    <title>data_checksums</title>
    <body>
C
Expand description of data_checksums GUC with checksum behavior and scope (#2945)  
Chuck Litzell 已提交
1040 1041 
      <p>Reports whether checksums are enabled for heap data storage in the database system.
        Checksums for heap data are enabled or disabled when the database system is initialized and
C
revise to more accurately describe failed checksum verify behavior (#2990)  
Chuck Litzell 已提交
1042 1043 
        cannot be changed. </p>
      <p>Heap data pages store heap tables, catalog tables, indexes, and database metadata.
C
Expand description of data_checksums GUC with checksum behavior and scope (#2945)  
Chuck Litzell 已提交
1044 1045 
        Append-optimized storage has built-in checksum support that is unrelated to this
        parameter.</p>
C
revise to more accurately describe failed checksum verify behavior (#2990)  
Chuck Litzell 已提交
1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 
      <p>Greenplum Database uses checksums to prevent loading data corrupted in the file system into
        memory managed by database processes. When heap data checksums are enabled, Greenplum
        Database computes and stores checksums on heap data pages when they are written to disk.
        When a page is retrieved from disk, the checksum is verified. If the verification fails, an
        error is generated and the page is not permitted to load into managed memory. </p>
      <p>If the <codeph>ignore_checksum_failure</codeph> configuration parameter has been set to on,
        a failed checksum verification generates a warning, but the page is allowed to be loaded
        into managed memory. If the page is then updated, it is flushed to disk and replicated to
        the mirror. This can cause data corruption to propagate to the mirror and prevent a complete
        recovery. Because of the potential for data loss, the
          <codeph>ignore_checksum_failure</codeph> parameter should only be enabled when needed to
        recover data. See <xref href="#ignore_checksum_failure" format="dita"/> for more
        information.</p>
C
Add heap checksums to gpinitsystem ref and GUC reference (#2915)  
Chuck Litzell 已提交
1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 
      <table id="table_djn_1nb_v1b">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">read only</entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 
  <topic id="DateStyle">
    <title>DateStyle</title>
    <body>
      <p>Sets the display format for date and time values, as well as the rules for interpreting
        ambiguous date input values. This variable contains two independent components: the output
        format specification and the input/output specification for year/month/day ordering.</p>
      <table id="DateStyle_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">&lt;format&gt;, &lt;date style&gt;<p>where:</p><p>&lt;format&gt;
                  is ISO, Postgres, SQL, or German</p><p>&lt;date style&gt; is DMY, MDY, or
                YMD</p></entry>
              <entry colname="col2">ISO, MDY</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="db_user_namespace">
    <title>db_user_namespace</title>
    <body>
      <p>This enables per-database user names. If on, you should create users as
          <i>username@dbname</i>. To create ordinary global users, simply append @ when specifying
        the user name in the client.</p>
      <table id="db_user_namespace_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="deadlock_timeout">
    <title>deadlock_timeout</title>
    <body>
      <p>The time to wait on a lock before checking to see if there is a deadlock condition. On a
        heavily loaded server you might want to raise this value. Ideally the setting should exceed
        your typical transaction time, so as to improve the odds that a lock will be released before
        the waiter decides to check for deadlock.</p>
      <table id="deadlock_timeout_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Any valid time expression (number and unit)</entry>
              <entry colname="col2">1s</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="debug_assertions">
    <title>debug_assertions</title>
    <body>
      <p>Turns on various assertion checks.</p>
      <table id="debug_assertions_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="debug_pretty_print">
    <title>debug_pretty_print</title>
    <body>
      <p>Indents debug output to produce a more readable but much longer output format.
          <i>client_min_messages</i> or <i>log_min_messages</i> must be DEBUG1 or lower.</p>
      <table id="debug_pretty_print_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
C
Docs updates to gucs (#7550)  
Chuck Litzell 已提交
1219 
              <entry colname="col2">on</entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="debug_print_parse">
    <title>debug_print_parse</title>
    <body>
      <p>For each executed query, prints the resulting parse tree. <i>client_min_messages</i> or
          <i>log_min_messages</i> must be DEBUG1 or lower.</p>
      <table id="debug_print_parse_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="debug_print_plan">
    <title>debug_print_plan</title>
    <body>
      <p>For each executed query, prints the Greenplum parallel query execution plan.
          <i>client_min_messages</i> or <i>log_min_messages</i> must be DEBUG1 or lower.</p>
      <table id="debug_print_plan_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="debug_print_prelim_plan">
    <title>debug_print_prelim_plan</title>
    <body>
      <p>For each executed query, prints the preliminary query plan. <i>client_min_messages</i> or
          <i>log_min_messages</i> must be DEBUG1 or lower.</p>
      <table id="debug_print_prelim_plan_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="debug_print_rewritten">
    <title>debug_print_rewritten</title>
    <body>
      <p>For each executed query, prints the query rewriter output. <i>client_min_messages</i> or
          <i>log_min_messages</i> must be DEBUG1 or lower.</p>
      <table id="debug_print_rewritten_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="debug_print_slice_table">
    <title>debug_print_slice_table</title>
    <body>
      <p>For each executed query, prints the Greenplum query slice plan. <i>client_min_messages</i>
        or <i>log_min_messages</i> must be DEBUG1 or lower.</p>
      <table id="debug_print_slice_table_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="default_statistics_target">
    <title>default_statistics_target</title>
    <body>
D
correcting range, defaults, and normalizing docs around default_statistics_target (#3819)  
David Yozie 已提交
1370 1371 1372 
      <p>Sets the default statistics sampling target (the number of values that are stored in the
        list of common values) for table columns that have not had a column-specific target set via
          <codeph>ALTER TABLE SET STATISTICS</codeph>. Larger values may improve the quality of the
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
1373 
        Postgres Planner estimates. </p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 
      <table id="default_statistics_target_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
M
DOCS update default and max values for GUC default_statistics_target. dev commit 18ca9e2968cf03  
mkiyama 已提交
1388 1389 
              <entry colname="col1"> 0 > Integer > 10000</entry>
              <entry colname="col2">100</entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="default_tablespace">
    <title>default_tablespace</title>
    <body>
      <p>The default tablespace in which to create objects (tables and indexes) when a
          <codeph>CREATE</codeph> command does not explicitly specify a tablespace.</p>
      <table id="default_tablespace_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">name of a tablespace</entry>
              <entry colname="col2">unset</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
C
Adds PostgreSQL full text search docs to GPDB docs (#6013)  
Chuck Litzell 已提交
1425 1426 1427 1428 1429 
  <topic id="default_text_search_config">
    <title>default_text_search_config</title>
    <body>
      <p>Selects the text search configuration that is used by those variants of the text search
        functions that do not have an explicit argument specifying the configuration. See <xref
M
docs - remove track_count GUC for pg_stat_* and pg_statio_* views (#6479)  
Mel Kiyama 已提交
1430 1431 1432 1433 1434 
          href="../../admin_guide/textsearch/full-text-search.xml#full-text-search"/> for further
        information. The built-in default is <codeph>pg_catalog.simple</codeph>, but
          <codeph>initdb</codeph> will initialize the configuration file with a setting that
        corresponds to the chosen <codeph>lc_ctype</codeph> locale, if a configuration matching that
        locale can be identified.</p>
C
Adds PostgreSQL full text search docs to GPDB docs (#6013)  
Chuck Litzell 已提交
1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 
      <table id="table_enc_3mb_lfb">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">The name of a text search configuration.</entry>
              <entry colname="col2"><codeph>pg_catalog.simple</codeph></entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Docs postgresql 9.1 merge (#6979)  
David Yozie 已提交
1458 1459 1460 
  <topic id="default_transaction_deferrable">
    <title>default_transaction_deferrable</title>
    <body>
M
docs -clarify GUC default_transaction_deferrable has not effect. (#8674)  
Mel Kiyama 已提交
1461 1462 1463 1464 1465 
      <p>When running at the <codeph>SERIALIZABLE</codeph> isolation level, a deferrable read-only
        SQL transaction may be delayed before it is allowed to proceed. However, once it begins
        executing it does not incur any of the overhead required to ensure serializability; so
        serialization code will have no reason to force it to abort because of concurrent updates,
        making this option suitable for long-running read-only transactions.</p>
D
Docs postgresql 9.1 merge (#6979)  
David Yozie 已提交
1466 1467 
      <p>This parameter controls the default deferrable status of each new transaction. It currently
        has no effect on read-write transactions or those operating at isolation levels lower than
M
docs -clarify GUC default_transaction_deferrable has not effect. (#8674)  
Mel Kiyama 已提交
1468 1469 1470 1471 1472 1473 
          <codeph>SERIALIZABLE</codeph>. The default is <codeph>off</codeph>.
        <note>Setting <codeph>default_transaction_deferrable</codeph> to <codeph>on</codeph> has no
          effect in Greenplum Database. Only read-only, <codeph>SERIALIZABLE</codeph> transactions
          can be deferred. However, Greenplum Database does not support the
            <codeph>SERIALIZABLE</codeph> transaction isolation level. See <xref
            href="../sql_commands/SET_TRANSACTION.xml"/>.</note></p>
D
Docs postgresql 9.1 merge (#6979)  
David Yozie 已提交
1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 
      <table id="default_transaction_deferrable">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>    
    </body>
  </topic>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
1497 1498 1499 
  <topic id="default_transaction_isolation">
    <title>default_transaction_isolation</title>
    <body>
C
docs - REPEATABLE READ xact mode is supported. (#6717)  
Chuck Litzell 已提交
1500 1501 1502 
      <p>Controls the default isolation level of each new transaction. Greenplum Database treats
          <codeph>read uncommitted</codeph> the same as <codeph>read committed</codeph>, and treats
          <codeph>serializable</codeph> the same as <codeph>repeatable read</codeph>. </p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 
      <table id="default_transaction_isolation_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
C
docs - REPEATABLE READ xact mode is supported. (#6717)  
Chuck Litzell 已提交
1517 1518 
              <entry colname="col1">read committed<p>read uncommitted</p><p>repeatable
                  read</p><p>serializable</p></entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 
              <entry colname="col2">read committed</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="default_transaction_read_only">
    <title>default_transaction_read_only</title>
    <body>
      <p>Controls the default read-only status of each new transaction. A read-only SQL transaction
        cannot alter non-temporary tables.</p>
      <table id="default_transaction_read_only_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="dynamic_library_path">
    <title>dynamic_library_path</title>
    <body>
      <p>If a dynamically loadable module needs to be opened and the file name specified in the
          <codeph>CREATE FUNCTION</codeph> or <codeph>LOAD</codeph> command does not have a
        directory component (i.e. the name does not contain a slash), the system will search this
        path for the required file. The compiled-in PostgreSQL package library directory is
        substituted for $libdir. This is where the modules provided by the standard PostgreSQL
        distribution are installed.</p>
      <table id="dynamic_library_path_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">a list of absolute directory paths separated by colons</entry>
              <entry colname="col2">$libdir</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="effective_cache_size">
    <title>effective_cache_size</title>
    <body>
      <p>Sets the assumption about the effective size of the disk cache that is available to a
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
1591 
        single query for the Postgres Planner. This is factored into estimates of
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
1592 1593 1594 1595 
        the cost of using an index; a higher value makes it more likely index scans will be used, a
        lower value makes it more likely sequential scans will be used. This parameter has no effect
        on the size of shared memory allocated by a Greenplum server instance, nor does it reserve
        kernel disk cache; it is used only for estimation purposes.</p>
C
Docs updates to gucs (#7550)  
Chuck Litzell 已提交
1596 1597 1598 1599 
      <p>Set this parameter to a number of 32K blocks (for example, <codeph>512</codeph> for 16MB),
        or specify the size of the effective cache (for example, <codeph>'32MB'</codeph> for 1024
        blocks). The <codeph>gpconfig</codeph> utility and <codeph>SHOW</codeph> command display the
        effective cache size value in units such as 'MB' or 'kB'.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 
      <table id="effective_cache_size_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">floating point</entry>
C
Docs updates to gucs (#7550)  
Chuck Litzell 已提交
1615 
              <entry colname="col2">512 (16GB)</entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="enable_bitmapscan">
    <title>enable_bitmapscan</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
1626 1627 
      <p>Enables or disables the use of bitmap-scan plan types by the Postgres Planner. Note that 
        this is different than a Bitmap Index Scan. A Bitmap Scan means that
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 
        indexes will be dynamically converted to bitmaps in memory when appropriate, giving faster
        index performance on complex queries against very large tables. It is used when there are
        multiple predicates on different indexed columns. Each bitmap per column can be compared to
        create a final list of selected tuples.</p>
      <table id="enable_bitmapscan_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="enable_groupagg">
    <title>enable_groupagg</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
1658 
      <p>Enables or disables the use of group aggregation plan types by the Postgres Planner.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 
      <table id="enable_groupagg_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="enable_hashagg">
    <title>enable_hashagg</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
1685 
      <p>Enables or disables the use of hash aggregation plan types by the Postgres Planner. </p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 
      <table id="enable_hashagg_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="enable_hashjoin">
    <title>enable_hashjoin</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
1712 
      <p>Enables or disables the use of hash-join plan types by the Postgres Planner.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 
      <table id="enable_hashjoin_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="enable_indexscan">
    <title>enable_indexscan</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
1739 
      <p>Enables or disables the use of index-scan plan types by the Postgres Planner.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 
      <table id="enable_indexscan_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="enable_mergejoin">
    <title>enable_mergejoin</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
1766 
      <p>Enables or disables the use of merge-join plan types by the Postgres Planner. Merge join is based on the idea of sorting the left- and right-hand tables into
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 
        order and then scanning them in parallel. So, both data types must be capable of being fully
        ordered, and the join operator must be one that can only succeed for pairs of values that
        fall at the 'same place' in the sort order. In practice this means that the join operator
        must behave like equality.</p>
      <table id="enable_mergejoin_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="enable_nestloop">
    <title>enable_nestloop</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
1797 1798 
      <p>Enables or disables the use of nested-loop join plans by the Postgres Planner. It's not possible to suppress nested-loop joins entirely, but turning this
        variable off discourages the Postgres Planner from using one if there are other methods
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 1824 1825 
        available. </p>
      <table id="enable_nestloop_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="enable_seqscan">
    <title>enable_seqscan</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
1826 1827 
      <p>Enables or disables the use of sequential scan plan types by the Postgres Planner. It's not possible to suppress sequential scans entirely, but turning this
        variable off discourages the Postgres Planner from using one if there are other methods
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 
        available.</p>
      <table id="enable_seqscan_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="enable_sort">
    <title>enable_sort</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
1855 
      <p>Enables or disables the use of explicit sort steps by the Postgres Planner.
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
1856 
        It's not possible to suppress explicit sorts entirely, but turning this variable off
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
1857 
        discourages the Postgres Planner from using one if there are other methods available.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 
      <table id="enable_sort_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="enable_tidscan">
    <title>enable_tidscan</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
1884 
      <p>Enables or disables the use of tuple identifier (TID) scan plan types by the Postgres Planner.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 
      <table id="enable_tidscan_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="escape_string_warning">
    <title>escape_string_warning</title>
    <body>
      <p>When on, a warning is issued if a backslash (\) appears in an ordinary string literal
        ('...' syntax). Escape string syntax (E'...') should be used for escapes, because in future
        versions, ordinary strings will have the SQL standard-conforming behavior of treating
        backslashes literally. </p>
      <table id="escape_string_warning_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="explain_pretty_print">
    <title>explain_pretty_print</title>
    <body>
      <p>Determines whether EXPLAIN VERBOSE uses the indented or non-indented format for displaying
        detailed query-tree dumps.</p>
      <table id="explain_pretty_print_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="extra_float_digits">
    <title>extra_float_digits</title>
    <body>
      <p>Adjusts the number of digits displayed for floating-point values, including float4, float8,
        and geometric data types. The parameter value is added to the standard number of digits. The
D
Docs: increase max of extra_float_digits to 3  
dyozie 已提交
1971 
        value can be set as high as 3, to include partially-significant digits; this is especially
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 
        useful for dumping float data that needs to be restored exactly. Or it can be set negative
        to suppress unwanted digits. </p>
      <table id="extra_float_digits_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
              <entry colname="col2">0</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="from_collapse_limit">
    <title>from_collapse_limit</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
2000 
      <p>The Postgres Planner will merge sub-queries into upper queries if the
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 2097 2098 2099 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 2113 2114 2115 2116 2117 2118 2119 2120 2121 2122 2123 2124 2125 2126 2127 2128 2129 2130 2131 2132 2133 2134 2135 2136 2137 2138 2139 2140 2141 2142 2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 2215 2216 2217 2218 2219 2220 2221 2222 2223 2224 2225 2226 2227 2228 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2241 2242 2243 2244 2245 2246 2247 2248 2249 2250 2251 2252 2253 2254 2255 2256 2257 2258 2259 2260 2261 2262 2263 2264 2265 2266 2267 2268 2269 2270 2271 2272 2273 2274 2275 2276 2277 2278 2279 2280 2281 2282 2283 2284 2285 2286 2287 2288 2289 2290 2291 2292 2293 2294 2295 2296 2297 2298 2299 2300 2301 2302 2303 2304 2305 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 2322 2323 2324 2325 2326 2327 2328 2329 2330 2331 2332 2333 2334 2335 2336 2337 2338 2339 2340 2341 2342 2343 2344 2345 2346 2347 2348 2349 2350 2351 2352 2353 2354 2355 2356 2357 2358 2359 2360 2361 2362 2363 2364 2365 2366 2367 2368 2369 2370 2371 2372 2373 2374 2375 2376 2377 
        resulting FROM list would have no more than this many items. Smaller values reduce planning
        time but may yield inferior query plans.</p>
      <table id="from_collapse_limit_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">1-<i>n</i></entry>
              <entry colname="col2">20</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_adjust_selectivity_for_outerjoins">
    <title>gp_adjust_selectivity_for_outerjoins</title>
    <body>
      <p>Enables the selectivity of NULL tests over outer joins.</p>
      <table id="gp_adjust_selectivity_for_outerjoins_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_appendonly_compaction">
    <title>gp_appendonly_compaction</title>
    <body>
      <p>Enables compacting segment files during <codeph>VACUUM</codeph> commands. When disabled,
          <codeph>VACUUM</codeph> only truncates the segment files to the EOF value, as is the
        current behavior. The administrator may want to disable compaction in high I/O load
        situations or low space situations. </p>
      <table id="gp_appendonly_compaction_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_appendonly_compaction_threshold">
    <title>gp_appendonly_compaction_threshold</title>
    <body>
      <p>Specifies the threshold ratio (as a percentage) of hidden rows to total rows that triggers
        compaction of the segment file when <cmdname>VACUUM</cmdname> is run without the
          <cmdname>FULL</cmdname> option (a lazy vacuum). If the ratio of hidden rows in a segment
        file on a segment is less than this threshold, the segment file is not compacted, and a log
        message is issued. </p>
      <table id="gp_appendonly_compaction_threshold_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer (%)</entry>
              <entry colname="col2">10</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_autostats_mode">
    <title>gp_autostats_mode</title>
    <body>
      <p>Specifies the mode for triggering automatic statistics collection with
          <codeph>ANALYZE</codeph>. The <codeph>on_no_stats</codeph> option triggers statistics
        collection for <codeph>CREATE TABLE AS SELECT</codeph>, <codeph>INSERT</codeph>, or
          <codeph>COPY</codeph> operations on any table that has no existing statistics.</p>
      <p>The <codeph>on_change</codeph> option triggers statistics collection only when the number
        of rows affected exceeds the threshold defined by
          <codeph>gp_autostats_on_change_threshold</codeph>. Operations that can trigger automatic
        statistics collection with <codeph>on_change</codeph> are:</p>
      <p>
        <codeph>CREATE TABLE AS SELECT</codeph>
      </p>
      <p>
        <codeph>UPDATE</codeph>
      </p>
      <p>
        <codeph>DELETE</codeph>
      </p>
      <p>
        <codeph>INSERT</codeph>
      </p>
      <p>
        <codeph>COPY</codeph>
      </p>
      <p>Default is <codeph>on_no_stats</codeph>. </p>
      <note>For partitioned tables, automatic statistics collection is not triggered if data is
        inserted from the top-level parent table of a partitioned table. <p>Automatic statistics
          collection is triggered if data is inserted directly in a leaf table (where the data is
          stored) of the partitioned table. Statistics are collected only on the leaf table.
        </p></note>
      <table id="gp_autostats_mode_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">none<p>on_change</p><p>on_no_stats</p></entry>
              <entry colname="col2">on_no_ stats</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_autostats_mode_in_functions">
    <title>gp_autostats_mode_in_functions</title>
    <body>
      <p>Specifies the mode for triggering automatic statistics collection with
          <codeph>ANALYZE</codeph> for statements in procedural language functions. The
          <codeph>none</codeph> option disables statistics collection. The
          <codeph>on_no_stats</codeph> option triggers statistics collection for <codeph>CREATE
          TABLE AS SELECT</codeph>, <codeph>INSERT</codeph>, or <codeph>COPY</codeph> operations
        that are executed in functions on any table that has no existing statistics.</p>
      <p>The <codeph>on_change</codeph> option triggers statistics collection only when the number
        of rows affected exceeds the threshold defined by
          <codeph>gp_autostats_on_change_threshold</codeph>. Operations in functions that can
        trigger automatic statistics collection with <codeph>on_change</codeph> are:</p>
      <p>
        <codeph>CREATE TABLE AS SELECT</codeph>
      </p>
      <p>
        <codeph>UPDATE</codeph>
      </p>
      <p>
        <codeph>DELETE</codeph>
      </p>
      <p>
        <codeph>INSERT</codeph>
      </p>
      <p>
        <codeph>COPY</codeph>
      </p>
      <table id="gp_autostats_mode_in_functions_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">none<p>on_change</p><p>on_no_stats</p></entry>
              <entry colname="col2">none</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_autostats_on_change_threshold">
    <title>gp_autostats_on_change_threshold</title>
    <body>
      <p>Specifies the threshold for automatic statistics collection when
          <codeph>gp_autostats_mode</codeph> is set to <codeph>on_change</codeph>. When a triggering
        table operation affects a number of rows exceeding this threshold, <codeph>ANALYZE
        </codeph>is added and statistics are collected for the table.</p>
      <table id="gp_autostats_on_change_threshold_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
              <entry colname="col2">2147483647</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_cached_segworkers_threshold">
    <title>gp_cached_segworkers_threshold</title>
    <body>
      <p>When a user starts a session with Greenplum Database and issues a query, the system creates
        groups or 'gangs' of worker processes on each segment to do the work. After the work is
        done, the segment worker processes are destroyed except for a cached number which is set by
        this parameter. A lower setting conserves system resources on the segment hosts, but a
        higher setting may improve performance for power-users that want to issue many complex
        queries in a row.</p>
      <table id="gp_cached_segworkers_threshold_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer &gt; 0</entry>
              <entry colname="col2">5</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_command_count">
    <title>gp_command_count</title>
    <body>
      <p>Shows how many commands the master has received from the client. Note that a single
        SQLcommand might actually involve more than one command internally, so the counter may
        increment by more than one for a single query. This counter also is shared by all of the
        segment processes working on the command.</p>
      <table id="gp_command_count_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer &gt; 0</entry>
              <entry colname="col2">1</entry>
              <entry colname="col3">read only</entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_connection_send_timeout">
    <title>gp_connection_send_timeout</title>
    <body>
      <p>Timeout for sending data to unresponsive Greenplum Database user clients during query
        processing. A value of 0 disables the timeout, Greenplum Database waits indefinitely for a
        client. When the timeout is reached, the query is cancelled with this
        message:<codeblock>Could not send data to client: Connection timed out.</codeblock></p>
      <table id="gp_connection_send_timeout_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">number of seconds</entry>
              <entry colname="col2">3600 (1 hour)</entry>
              <entry colname="col3">master<p>system</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_content">
    <title>gp_content</title>
    <body>
      <p>The local content id if a segment.</p>
      <table id="gp_content_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
              <entry colname="col2"/>
              <entry colname="col3">read only</entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_create_table_random_default_distribution">
    <title>gp_create_table_random_default_distribution</title>
    <body>
      <p>Controls table creation when a Greenplum Database table is created with a <cmdname>CREATE
          TABLE</cmdname> or <cmdname>CREATE TABLE AS</cmdname> command that does not contain a
          <cmdname>DISTRIBUTED BY</cmdname> clause.</p>
      <p>For <cmdname>CREATE TABLE</cmdname>, if the value of the parameter is <codeph>off</codeph>
        (the default), and the table creation command does not contain a <cmdname>DISTRIBUTED
          BY</cmdname> clause, Greenplum Database chooses the table distribution key based on the
D
Update gp_create_table_random_default_distribution to describe 6.x rules (#6145)  
David Yozie 已提交
2378 2379 2380 2381 2382 2383 2384 2385 2386 2387 2388 
          command:<ul id="ul_rjb_gty_qfb">
          <li>If a <codeph>LIKE</codeph> or <codeph>INHERITS</codeph> clause is specified, then
            Greenplum copies the distribution key from the source or parent table.</li>
          <li>If a <codeph>PRIMARY KEY</codeph> or <codeph>UNIQUE</codeph> constraints are
            specified, then Greenplum chooses the largest subset of all the key columns as the
            distribution key.</li>
          <li>If neither constraints nor a <codeph>LIKE</codeph> or <codeph>INHERITS</codeph> clause
            is specified, then Greenplum chooses the first suitable column as the distribution key.
            (Columns with geometric or user-defined data types are not eligible as Greenplum
            distribution key columns.)</li>
        </ul></p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2389 2390 2391 2392 2393 2394 2395 2396 2397 2398 2399 2400 2401 2402 
      <p>If the value of the parameter is set to <codeph>on</codeph>, Greenplum Database follows
        these rules to create a table when the <cmdname>DISTRIBUTED BY</cmdname> clause is not
          specified:<ul id="ul_tbr_5kq_kq">
          <li>If <cmdname>PRIMARY KEY</cmdname> or <cmdname>UNIQUE</cmdname> columns are not
            specified, the distribution of the table is random (<cmdname>DISTRIBUTED
              RANDOMLY</cmdname>). Table distribution is random even if the table creation command
            contains the <cmdname>LIKE</cmdname> or <cmdname>INHERITS</cmdname> clause. </li>
          <li>If <cmdname>PRIMARY KEY</cmdname> or <cmdname>UNIQUE</cmdname> columns are specified,
            a <cmdname>DISTRIBUTED BY</cmdname> clause must also be specified. If a
              <cmdname>DISTRIBUTED BY</cmdname> clause is not specified as part of the table
            creation command, the command fails.</li>
        </ul></p>
      <p>For a <cmdname>CREATE TABLE AS</cmdname> command that does not contain a distribution
          clause:<ul id="ul_ejv_m1b_kr">
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
2403 
          <li>If the Postgres Planner creates the table, and the value of the parameter is
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2404 2405 
              <codeph>off</codeph>, the table distribution policy is determined based on the
            command.</li>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
2406 
          <li>If the Postgres Planner creates the table, and the value of the parameter is
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2407 2408 2409 2410 
              <codeph>on</codeph>, the table distribution policy is random.</li>
          <li>If GPORCA creates the table, the table distribution policy is random. The parameter
            value has no affect. </li>
        </ul></p>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
2411 
      <p>For information about the Postgres Planner and GPORCA, see "Querying Data" in the
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2412 2413 2414 2415 2416 2417 2418 2419 2420 2421 2422 2423 2424 2425 2426 2427 2428 2429 2430 2431 2432 2433 2434 2435 2436 2437 2438 2439 2440 2441 2442 2443 2444 2445 2446 2447 2448 2449 2450 2451 2452 2453 2454 2455 2456 2457 2458 2459 2460 2461 2462 2463 2464 2465 2466 2467 2468 2469 2470 2471 2472 2473 2474 2475 2476 2477 2478 2479 2480 2481 2482 2483 2484 2485 2486 2487 2488 2489 2490 2491 2492 2493 
          <cite>Greenplum Database Administrator Guide</cite>. </p>
      <table id="table_hh5_kgp_kq">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>system</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_dbid">
    <title>gp_dbid</title>
    <body>
      <p>The local content dbid if a segment.</p>
      <table id="gp_dbid_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
              <entry colname="col2"/>
              <entry colname="col3">read only</entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_debug_linger">
    <title>gp_debug_linger</title>
    <body>
      <p>Number of seconds for a Greenplum process to linger after a fatal internal error.</p>
      <table id="gp_debug_linger_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Any valid time expression (number and unit)</entry>
              <entry colname="col2">0</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_default_storage_options">
    <title>gp_default_storage_options</title>
    <body>
      <p>Set the default values for the following table storage options when a table is created with
L
docs - appendoptimized is an alias for appendonly storage option (#6925)  
Lisa Owen 已提交
2494 2495 2496 2497 2498 2499 2500 
        the <codeph>CREATE TABLE</codeph> command.<ul id="ul_r4t_nxx_5p">
          <li><cmdname>appendoptimized</cmdname>
            <note>You use the <codeph>appendoptimized=<varname>value</varname></codeph> syntax
              to specify the append-optimized table storage type. <codeph>appendoptimized</codeph>
              is a thin alias for the <codeph>appendonly</codeph> legacy storage option. Greenplum
              Database stores <codeph>appendonly</codeph> in the catalog, and displays the
              same when listing the storage options for append-optimized tables.</note>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2501 
          </li>
L
docs - appendoptimized is an alias for appendonly storage option (#6925)  
Lisa Owen 已提交
2502 
          <li><cmdname>blocksize</cmdname>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2503 
          </li>
L
docs - appendoptimized is an alias for appendonly storage option (#6925)  
Lisa Owen 已提交
2504 2505 
          <li><cmdname>checksum</cmdname></li>
          <li><cmdname>compresstype</cmdname>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2506 
          </li>
L
docs - appendoptimized is an alias for appendonly storage option (#6925)  
Lisa Owen 已提交
2507 
          <li><cmdname>compresslevel</cmdname>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2508 
          </li>
L
docs - appendoptimized is an alias for appendonly storage option (#6925)  
Lisa Owen 已提交
2509 
          <li><cmdname>orientation</cmdname>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2510 2511 2512 2513 
          </li>
        </ul></p>
      <p>Specify multiple storage option values as a comma separated list.</p>
      <p>You can set the storage options with this parameter instead of specifying the table storage
L
docs - appendoptimized is an alias for appendonly storage option (#6925)  
Lisa Owen 已提交
2514 2515 
        options in the <codeph>WITH</codeph> of the <codeph>CREATE TABLE</codeph> command. The
        table storage options that are specified with the <codeph>CREATE TABLE</codeph> command
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2516 2517 
        override the values specified by this parameter. </p>
      <p>Not all combinations of storage option values are valid. If the specified storage options
L
docs - appendoptimized is an alias for appendonly storage option (#6925)  
Lisa Owen 已提交
2518 
        are not valid, an error is returned. See the <codeph>CREATE TABLE</codeph> command for
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2519 2520 2521 2522 2523 
        information about table storage options. </p>
      <p>The defaults can be set for a database and user. If the server configuration parameter is
        set at different levels, this the order of precedence, from highest to lowest, of the table
        storage values when a user logs into a database and creates a table:</p>
      <ol id="ol_fy1_fty_5p">
L
docs - appendoptimized is an alias for appendonly storage option (#6925)  
Lisa Owen 已提交
2524 2525 
        <li>The values specified in a <codeph>CREATE TABLE</codeph> command with the
            <codeph>WITH</codeph> clause or <codeph>ENCODING</codeph> clause</li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2526 
        <li>The value of <codeph>gp_default_storage_options</codeph> that set for the user with the
L
docs - appendoptimized is an alias for appendonly storage option (#6925)  
Lisa Owen 已提交
2527 
            <codeph>ALTER ROLE...SET</codeph> command</li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2528 
        <li>The value of <codeph>gp_default_storage_options</codeph> that is set for the database
L
docs - appendoptimized is an alias for appendonly storage option (#6925)  
Lisa Owen 已提交
2529 
          with the <codeph>ALTER DATABASE...SET</codeph> command</li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2530 
        <li>The value of <codeph>gp_default_storage_options</codeph> that is set for the Greenplum
L
docs - appendoptimized is an alias for appendonly storage option (#6925)  
Lisa Owen 已提交
2531 
          Database system with the <codeph>gpconfig</codeph> utility</li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2532 2533 
      </ol>
      <p>The parameter value is not cumulative. For example, if the parameter specifies the
L
docs - appendoptimized is an alias for appendonly storage option (#6925)  
Lisa Owen 已提交
2534 
          <codeph>appendoptimized</codeph> and <codeph>compresstype</codeph> options for a database
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2535 
        and a user logs in and sets the parameter to specify the value for the
L
docs - appendoptimized is an alias for appendonly storage option (#6925)  
Lisa Owen 已提交
2536 2537 2538 2539 2540 
          <codeph>orientation</codeph> option, the <codeph>appendoptimized</codeph>, and
          <codeph>compresstype</codeph> values set at the database level are ignored. </p>
      <p>This example <codeph>ALTER DATABASE</codeph> command sets the default
          <codeph>orientation</codeph> and <codeph>compresstype</codeph> table storage options
        for the database <codeph>mytest</codeph>.
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2541 2542 2543 
        <codeblock>ALTER DATABASE mytest SET gp_default_storage_options = 'orientation=column, compresstype=rle_type'</codeblock></p>
      <p>To create an append-optimized table in the <codeph>mytest</codeph> database with
        column-oriented table and RLE compression. The user needs to specify only
L
docs - appendoptimized is an alias for appendonly storage option (#6925)  
Lisa Owen 已提交
2544 2545 
          <codeph>appendoptimized=TRUE</codeph> in the <codeph>WITH</codeph> clause.</p>
      <p>This example <codeph>gpconfig</codeph> utility command sets the default storage option
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2546 
        for a Greenplum Database system. If you set the defaults for multiple table storage options,
M
DOCS: update gpconfig. Updated, simplified quoting syntax for GUC values (#3016)  
Mel Kiyama 已提交
2547 
        the value must be enclosed in single
L
docs - appendoptimized is an alias for appendonly storage option (#6925)  
Lisa Owen 已提交
2548 2549 
        quotes.<codeblock>gpconfig -c 'gp_default_storage_options' -v 'appendoptimized=true, orientation=column'</codeblock></p>
      <p>This example <codeph>gpconfig</codeph> utility command shows the value of the parameter.
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2550 2551 2552 2553 2554 2555 2556 2557 2558 2559 2560 2561 2562 2563 2564 2565 
        The parameter value must be consistent across the Greenplum Database master and all
        segments.<codeblock>gpconfig -s 'gp_default_storage_options'</codeblock></p>
      <table id="gp_default_storage_option_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications <sup>1</sup></entry>
            </row>
          </thead>
          <tbody>
            <row>
L
docs - appendoptimized is an alias for appendonly storage option (#6925)  
Lisa Owen 已提交
2566 2567 2568 
              <entry colname="col1"><codeph>appendoptimized</codeph>= <codeph>TRUE</codeph> |
                  <codeph>FALSE</codeph><p><codeph>blocksize</codeph>= integer between 8192 and
                  2097152 </p><p><codeph>checksum</codeph>= <codeph>TRUE</codeph> |
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2569 
                    <codeph>FALSE</codeph>
L
docs - appendoptimized is an alias for appendonly storage option (#6925)  
Lisa Owen 已提交
2570 
                </p><p><codeph>compresstype</codeph>= <codeph>ZLIB</codeph> |
M
docs: add guc gp_max_slices (#4854)  
Mel Kiyama 已提交
2571 
                    <codeph>ZSTD</codeph> | <codeph>QUICKLZ</codeph><sup>2</sup> |
L
qualify quicklz references (#1686)  
Lisa Owen 已提交
2572 
                    <codeph>RLE</codeph>_<codeph>TYPE</codeph> | <codeph>NONE</codeph>
L
docs - appendoptimized is an alias for appendonly storage option (#6925)  
Lisa Owen 已提交
2573 2574 
                </p><p><codeph>compresslevel</codeph>= integer between 0 and
                    19</p><p><codeph>orientation</codeph>= <codeph>ROW</codeph> |
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2575 2576 
                    <codeph>COLUMN</codeph>
                </p></entry>
L
docs - appendoptimized is an alias for appendonly storage option (#6925)  
Lisa Owen 已提交
2577 2578 2579 2580 2581 2582 
              <entry colname="col2"><codeph>appendoptimized</codeph>=<codeph>FALSE</codeph>
                <p><codeph>blocksize</codeph>=<codeph>32768</codeph>
                </p><p><codeph>checksum</codeph>=<codeph>TRUE</codeph>
                </p><p><codeph>compresstype</codeph>=<codeph>none</codeph>
                </p><p><codeph>compresslevel</codeph>=<codeph>0</codeph>
                </p><p><codeph>orientation</codeph>=<codeph>ROW</codeph></p></entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2583 2584 2585 2586 2587 2588 2589 
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
      <note>
        <sup>1</sup>The set classification when the parameter is set at the system level with the
L
docs - appendoptimized is an alias for appendonly storage option (#6925)  
Lisa Owen 已提交
2590 
          <codeph>gpconfig</codeph> utility.</note>
L
qualify quicklz references (#1686)  
Lisa Owen 已提交
2591 2592 2593 
      <note>
        <sup>2</sup>QuickLZ compression is available only in the commercial release of Pivotal
        Greenplum Database.</note>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2594 2595 2596 2597 2598 2599 2600 2601 2602 2603 2604 2605 2606 2607 2608 2609 2610 2611 2612 2613 2614 2615 2616 2617 2618 2619 2620 2621 2622 2623 2624 2625 2626 2627 2628 2629 2630 2631 2632 2633 2634 2635 2636 2637 2638 2639 2640 2641 2642 2643 2644 2645 2646 2647 2648 2649 2650 2651 2652 2653 2654 2655 2656 2657 2658 2659 2660 2661 2662 2663 2664 2665 2666 2667 2668 2669 2670 2671 2672 2673 2674 2675 2676 2677 2678 2679 2680 2681 2682 2683 2684 2685 2686 2687 2688 2689 2690 2691 2692 2693 2694 2695 2696 2697 2698 2699 2700 2701 2702 2703 2704 2705 2706 2707 2708 2709 2710 2711 2712 2713 2714 2715 2716 2717 2718 2719 2720 2721 2722 2723 2724 2725 2726 2727 2728 2729 2730 2731 2732 2733 2734 2735 2736 2737 2738 2739 2740 2741 2742 2743 2744 2745 2746 2747 2748 2749 2750 2751 2752 2753 2754 2755 
    </body>
  </topic>
  <topic id="gp_dynamic_partition_pruning">
    <title>gp_dynamic_partition_pruning</title>
    <body>
      <p>Enables plans that can dynamically eliminate the scanning of partitions.</p>
      <table id="gp_dynamic_partition_pruning_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">on/off</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_enable_agg_distinct">
    <title>gp_enable_agg_distinct</title>
    <body>
      <p>Enables or disables two-phase aggregation to compute a single distinct-qualified aggregate.
        This applies only to subqueries that include a single distinct-qualified aggregate
        function.</p>
      <table id="gp_enable_agg_distinct_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_enable_agg_distinct_pruning">
    <title>gp_enable_agg_distinct_pruning</title>
    <body>
      <p>Enables or disables three-phase aggregation and join to compute distinct-qualified
        aggregates. This applies only to subqueries that include one or more distinct-qualified
        aggregate functions.</p>
      <table id="gp_enable_agg_distinct_pruning_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_enable_direct_dispatch">
    <title>gp_enable_direct_dispatch</title>
    <body>
      <p>Enables or disables the dispatching of targeted query plans for queries that access data on
        a single segment. When on, queries that target rows on a single segment will only have their
        query plan dispatched to that segment (rather than to all segments). This significantly
        reduces the response time of qualifying queries as there is no interconnect setup involved.
        Direct dispatch does require more CPU utilization on the master.</p>
      <table id="gp_enable_direct_dispatch_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_enable_exchange_default_partition">
    <title>gp_enable_exchange_default_partition</title>
    <body>
      <p>Controls availability of the <codeph>EXCHANGE DEFAULT PARTITION</codeph> clause for
          <codeph>ALTER TABLE</codeph>. The default value for the parameter is <codeph>off</codeph>.
        The clause is not available and Greenplum Database returns an error if the clause is
        specified in an <codeph>ALTER TABLE</codeph> command. </p>
      <p>If the value is <codeph>on</codeph>, Greenplum Database returns a warning stating that
        exchanging the default partition might result in incorrect results due to invalid data in
        the default partition.</p>
      <p>
        <note type="warning">Before you exchange the default partition, you must ensure the data in
          the table to be exchanged, the new default partition, is valid for the default partition.
          For example, the data in the new default partition must not contain data that would be
          valid in other leaf child partitions of the partitioned table. Otherwise, queries against
          the partitioned table with the exchanged default partition that are executed by GPORCA
          might return incorrect results.</note>
      </p>
      <table id="gp_enable_exchange_default_partition_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_enable_fast_sri">
    <title>gp_enable_fast_sri</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
2756 
      <p>When set to <codeph>on</codeph>, the Postgres Planner plans single row
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2757 2758 2759 2760 2761 2762 2763 2764 2765 2766 2767 2768 2769 2770 2771 2772 2773 2774 2775 2776 2777 2778 2779 2780 2781 
        inserts so that they are sent directly to the correct segment instance (no motion operation
        required). This significantly improves performance of single-row-insert statements.</p>
      <table id="gp_enable_fast_sri_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
M
docs - add GUC gp_enable_global_deadlock_detector (#6894)  
Mel Kiyama 已提交
2782 2783 2784 2785 2786 2787 2788 2789 2790 
  <topic id="gp_enable_global_deadlock_detector">
    <title>gp_enable_global_deadlock_detector</title>
    <body>
      <p>Controls whether the Greenplum Database Global Deadlock Detector is enabled to manage
        concurrent <codeph>UPDATE</codeph> and <codeph>DELETE</codeph> operations on heap tables to
        improve performance. See <xref href="../../admin_guide/dml.xml#topic_gdd"/><ph
          otherprops="op-print"> in the <cite>Greenplum Database Administrator Guide</cite></ph>.
        The default is <codeph>off</codeph>, the Global Deadlock Detector is disabled. </p>
      <p>If the Global Deadlock Detector is disabled (the default), Greenplum Database executes
M
docs - GDD - add information about specific type of deadlocks. (#7014)  
Mel Kiyama 已提交
2791 2792 2793 2794 2795 
        concurrent update and delete operations on a heap table serially.</p>
      <p>If the Global Deadlock Detector is enabled, concurrent updates are permitted and the Global 
        Deadlock Detector determines when a deadlock exists, and
        breaks the deadlock by cancelling one or more backend processes associated with the youngest
        transaction(s) involved. </p>
M
docs - add GUC gp_enable_global_deadlock_detector (#6894)  
Mel Kiyama 已提交
2796 2797 2798 2799 2800 2801 2802 2803 2804 2805 2806 2807 2808 2809 2810 2811 
      <table id="table_vcm_p3r_qgb">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
M
docs - GDD - add information about specific type of deadlocks. (#7014)  
Mel Kiyama 已提交
2812 
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
M
docs - add GUC gp_enable_global_deadlock_detector (#6894)  
Mel Kiyama 已提交
2813 2814 2815 2816 2817 2818 
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2819 2820 2821 
  <topic id="gp_enable_gpperfmon">
    <title>gp_enable_gpperfmon</title>
    <body>
M
GPDB DOCS update set classifications for GUC standard_conforming_strings  
mkiyama 已提交
2822 
      <p>Enables or disables the data collection agents that populate the <codeph>gpperfmon</codeph>
C
docs - GPCC no longer depends on gpperfmon_install (#7972)  
Chuck Litzell 已提交
2823 
        database.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2824 2825 2826 2827 2828 2829 2830 2831 2832 2833 2834 2835 2836 2837 2838 2839 2840 2841 2842 2843 2844 2845 2846 2847 2848 2849 2850 2851 
      <table id="gp_enable_gpperfmon_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_enable_groupext_distinct_gather">
    <title>gp_enable_groupext_distinct_gather</title>
    <body>
      <p>Enables or disables gathering data to a single node to compute distinct-qualified
        aggregates on grouping extension queries. When this parameter and
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
2852 
          <codeph>gp_enable_groupext_distinct_pruning</codeph> are both enabled, the Postgres Planner uses the cheaper plan.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2853 2854 2855 2856 2857 2858 2859 2860 2861 2862 2863 2864 2865 2866 2867 2868 2869 2870 2871 2872 2873 2874 2875 2876 2877 2878 2879 2880 
      <table id="gp_enable_groupext_distinct_gather_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_enable_groupext_distinct_pruning">
    <title>gp_enable_groupext_distinct_pruning</title>
    <body>
      <p>Enables or disables three-phase aggregation and join to compute distinct-qualified
        aggregates on grouping extension queries. Usually, enabling this parameter generates a
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
2881 
        cheaper query plan that the Postgres Planner will use in preference to
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2882 2883 2884 2885 2886 2887 2888 2889 2890 2891 2892 2893 2894 2895 2896 2897 2898 2899 2900 2901 2902 2903 2904 2905 2906 2907 2908 
        existing plan.</p>
      <table id="gp_enable_groupext_distinct_pruning_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_enable_multiphase_agg">
    <title>gp_enable_multiphase_agg</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
2909 2910 
      <p>Enables or disables the use of two or three-stage parallel aggregation plans Postgres Planner. 
        This approach applies to any subquery with aggregation. If
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2911 2912 2913 2914 2915 2916 2917 2918 2919 2920 2921 2922 2923 2924 2925 2926 2927 2928 2929 2930 2931 2932 2933 2934 2935 2936 2937 2938 2939 
          <codeph>gp_enable_multiphase_agg</codeph> is off, then<codeph>
          gp_enable_agg_distinct</codeph> and <codeph>gp_enable_agg_distinct_pruning</codeph> are
        disabled.</p>
      <table id="gp_enable_multiphase_agg_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_enable_predicate_propagation">
    <title>gp_enable_predicate_propagation</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
2940 
      <p>When enabled, the Postgres Planner applies query predicates to both table
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
2941 2942 2943 2944 2945 2946 2947 2948 2949 2950 2951 2952 2953 2954 2955 2956 2957 2958 2959 2960 2961 2962 2963 2964 2965 2966 2967 2968 2969 2970 2971 2972 2973 2974 2975 2976 2977 2978 2979 2980 2981 2982 2983 2984 2985 2986 2987 2988 2989 2990 2991 2992 2993 2994 2995 2996 
        expressions in cases where the tables are joined on their distribution key column(s).
        Filtering both tables prior to doing the join (when possible) is more efficient.</p>
      <table id="gp_enable_predicate_propagation_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_enable_preunique">
    <title>gp_enable_preunique</title>
    <body>
      <p>Enables two-phase duplicate removal for <codeph>SELECT DISTINCT</codeph> queries (not
          <codeph>SELECT COUNT(DISTINCT)</codeph>). When enabled, it adds an extra <codeph>SORT
          DISTINCT</codeph> set of plan nodes before motioning. In cases where the distinct
        operation greatly reduces the number of rows, this extra <codeph>SORT DISTINCT</codeph> is
        much cheaper than the cost of sending the rows across the Interconnect.</p>
      <table id="gp_enable_preunique_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
C
docs: add real-time query metrics GUCs to reference (#4618)  
Chuck Litzell 已提交
2997 2998 2999 
  <topic id="gp_enable_query_metrics">
    <title>gp_enable_query_metrics</title>
    <body>
M
docs: add guc gp_max_slices (#4854)  
Mel Kiyama 已提交
3000 3001 3002 
      <p>Enables collection of query metrics. When query metrics collection is enabled, Greenplum
        Database collects metrics during query execution. The default is off.</p>
      <p>After changing this configuration parameter, Greenplum Database must be restarted for the
C
docs: add real-time query metrics GUCs to reference (#4618)  
Chuck Litzell 已提交
3003 
        change to take effect.</p>
M
docs: add guc gp_max_slices (#4854)  
Mel Kiyama 已提交
3004 3005 3006 3007 
      <p>The Greenplum Database metrics collection extension, when enabled, sends the collected
        metrics over UDP to a Pivotal Greenplum Command Center agent<sup>1</sup>. </p>
      <note><sup>1</sup> The metrics collection extension is included in Pivotal's commercial
        version of Greenplum Database. Pivotal Greenplum Command Center is supported only with
C
docs: add real-time query metrics GUCs to reference (#4618)  
Chuck Litzell 已提交
3008 3009 3010 3011 3012 3013 3014 3015 3016 3017 3018 3019 3020 3021 3022 3023 3024 3025 3026 3027 3028 3029 3030 3031 
        Pivotal Greenplum Database.</note>
      <table id="gp_enable_query_metrics">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
M
DOCS: New GUC gp_enable_segment_copy_checking. COPY ON SEGMENT changes (#3046)  
Mel Kiyama 已提交
3032 3033 3034 
  <topic id="gp_enable_relsize_collection">
    <title>gp_enable_relsize_collection</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
3035 
      <p>Enables GPORCA and the Postgres Planner to use the estimated size of a
M
docs - update guc gp_enable_relsize_collection - ORCA support (#5339)  
Mel Kiyama 已提交
3036 3037 3038 3039 3040 3041 3042 3043 
        table (<codeph>pg_relation_size</codeph> function) if there are no statistics for the table.
        By default, GPORCA and the planner use a default value to estimate the number of rows if
        statistics are not available. The default behavior improves query optimization time and
        reduces resource queue usage in heavy workloads, but can lead to suboptimal plans.</p>
      <p>This parameter is ignored for a root partition of a partitioned table. When GPORCA is
        enabled and the root partition does not have statistics, GPORCA always uses the default
        value. You can use <codeph>ANALZYE ROOTPARTITION</codeph> to collect statistics on the root
        partition. See <codeph><xref href="../../ref_guide/sql_commands/ANALYZE.xml"/></codeph>.</p>
M
DOCS: New GUC gp_enable_segment_copy_checking. COPY ON SEGMENT changes (#3046)  
Mel Kiyama 已提交
3044 3045 3046 3047 3048 3049 3050 3051 3052 3053 3054 3055 3056 3057 3058 3059 3060 3061 3062 3063 3064 3065 3066 3067 3068 
      <table id="table_b2v_b5t_3x">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_enable_segment_copy_checking">
    <title>gp_enable_segment_copy_checking</title>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
3069 
    <body>
M
DOCS: New GUC gp_enable_segment_copy_checking. COPY ON SEGMENT changes (#3046)  
Mel Kiyama 已提交
3070 
      <p>Controls whether the distribution policy for a table (from the table
M
docs - remove track_count GUC for pg_stat_* and pg_statio_* views (#6479)  
Mel Kiyama 已提交
3071 3072 3073 3074 
          <codeph>DISTRIBUTED</codeph> clause) is checked when data is copied into the table with
        the <codeph>COPY FROM...ON SEGMENT</codeph> command. If true, an error is returned if a row
        of data violates the distribution policy for a segment instance. The default is
          <codeph>true</codeph>. </p>
M
DOCS: COPY cmd. - remove reference to ALTER TABLE clause WITH REORGANIZE (#3127)  
Mel Kiyama 已提交
3075 3076 
      <p>If the value is <codeph>false</codeph>, the distribution policy is not checked. The data
        added to the table might violate the table distribution policy for the segment instance.
M
docs: COPY command - add PROGRAM clause (#3297)  
Mel Kiyama 已提交
3077 3078 
        Manual redistribution of table data might be required. See the <codeph>ALTER TABLE</codeph>
        clause <codeph>WITH REORGANIZE</codeph>.</p>
M
DOCS: COPY cmd. - remove reference to ALTER TABLE clause WITH REORGANIZE (#3127)  
Mel Kiyama 已提交
3079 3080 
      <p>The parameter can be set for a database system or a session. The parameter cannot be set
        for a specific database.</p>
M
DOCS: New GUC gp_enable_segment_copy_checking. COPY ON SEGMENT changes (#3046)  
Mel Kiyama 已提交
3081 
      <table id="table_gxf_hpm_z1b">
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
3082 3083 3084 3085 3086 3087 3088 3089 3090 3091 3092 3093 3094 3095 
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
M
DOCS: New GUC gp_enable_segment_copy_checking. COPY ON SEGMENT changes (#3046)  
Mel Kiyama 已提交
3096 
              <entry colname="col2">true</entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
3097 3098 3099 3100 3101 3102 3103 3104 3105 3106 3107 3108 3109 3110 3111 3112 3113 3114 3115 3116 3117 3118 3119 3120 3121 3122 3123 3124 3125 3126 3127 3128 3129 3130 3131 3132 3133 3134 3135 3136 3137 3138 3139 3140 3141 3142 3143 3144 3145 3146 3147 3148 3149 3150 3151 3152 3153 3154 3155 3156 3157 3158 3159 3160 3161 3162 3163 3164 3165 3166 3167 3168 3169 3170 3171 3172 3173 3174 3175 3176 3177 3178 3179 3180 3181 3182 3183 3184 3185 3186 3187 3188 3189 3190 3191 3192 3193 3194 3195 3196 3197 3198 3199 3200 3201 3202 3203 3204 3205 3206 3207 3208 3209 3210 3211 3212 3213 3214 3215 3216 3217 
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_enable_sort_distinct">
    <title>gp_enable_sort_distinct</title>
    <body>
      <p>Enable duplicates to be removed while sorting.</p>
      <table id="gp_enable_sort_distinct_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_enable_sort_limit">
    <title>gp_enable_sort_limit</title>
    <body>
      <p>Enable <codeph>LIMIT</codeph> operation to be performed while sorting. Sorts more
        efficiently when the plan requires the first <i>limit_number</i> of rows at most.</p>
      <table id="gp_enable_sort_limit_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_external_enable_exec">
    <title>gp_external_enable_exec</title>
    <body>
      <p>Enables or disables the use of external tables that execute OS commands or scripts on the
        segment hosts (<codeph>CREATE EXTERNAL TABLE EXECUTE</codeph> syntax). <ph>Must be enabled
          if using the Command Center or MapReduce features.</ph></p>
      <table id="gp_external_enable_exec_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_external_max_segs">
    <title>gp_external_max_segs</title>
    <body>
      <p>Sets the number of segments that will scan external table data during an external table
        operation, the purpose being not to overload the system with scanning data and take away
        resources from other concurrent operations. This only applies to external tables that use
        the <codeph>gpfdist://</codeph> protocol to access external table data.</p>
      <table id="gp_external_max_segs_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
              <entry colname="col2">64</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
I
Implement filter pushdown for PXF data sources (#4968)  
Ivan Leskin 已提交
3218 3219 3220 
  <topic id="gp_external_enable_filter_pushdown">
    <title>gp_external_enable_filter_pushdown</title>
    <body>
M
docs - add GUC gp_resource_group_bypass (#5231)  
Mel Kiyama 已提交
3221 
      <p>Enable filter pushdown when reading data from external tables. If pushdown fails, a query
D
Docs: Edit pxf filter pushdown docs (#5219)  
David Yozie 已提交
3222 3223 3224 
        is executed without pushing filters to the external data source (instead, Greenplum Database
        applies the same constraints to the result). See <xref
          href="../../admin_guide/external/g-external-tables.xml#topic3"/> for more information.</p>
I
Implement filter pushdown for PXF data sources (#4968)  
Ivan Leskin 已提交
3225 3226 3227 3228 3229 3230 3231 3232 3233 3234 3235 3236 3237 3238 3239 
      <table id="enable_filter_pushdown_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
A
Default gp_external_enable_filter_pushdown GUC to true and fix to handle both...  
Alexander Denissov 已提交
3240 
              <entry colname="col2">on</entry>
I
Implement filter pushdown for PXF data sources (#4968)  
Ivan Leskin 已提交
3241 3242 3243 3244 3245 3246 3247 
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
3248 3249 3250 3251 3252 3253 3254 3255 3256 3257 3258 3259 3260 3261 3262 3263 3264 3265 3266 3267 3268 3269 3270 3271 3272 3273 3274 3275 3276 3277 3278 3279 3280 3281 3282 3283 3284 3285 3286 3287 3288 3289 3290 3291 3292 3293 3294 3295 3296 3297 3298 3299 3300 3301 3302 3303 3304 3305 3306 3307 3308 3309 3310 3311 3312 3313 3314 3315 3316 3317 3318 3319 3320 3321 3322 3323 3324 3325 3326 3327 3328 3329 3330 3331 3332 3333 3334 3335 3336 3337 3338 3339 3340 3341 3342 3343 3344 3345 3346 3347 3348 3349 3350 3351 3352 3353 3354 3355 3356 3357 3358 3359 3360 
  <topic id="gp_fts_probe_interval">
    <title>gp_fts_probe_interval</title>
    <body>
      <p>Specifies the polling interval for the fault detection process (<codeph>ftsprobe</codeph>).
        The <codeph>ftsprobe</codeph> process will take approximately this amount of time to detect
        a segment failure.</p>
      <table id="gp_fts_probe_interval_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">10 - 3600 seconds</entry>
              <entry colname="col2">1min</entry>
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_fts_probe_retries">
    <title>gp_fts_probe_retries</title>
    <body>
      <p>Specifies the number of times the fault detection process (<codeph>ftsprobe</codeph>)
        attempts to connect to a segment before reporting segment failure. </p>
      <table id="gp_fts_probe_retries_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
              <entry colname="col2">5</entry>
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_fts_probe_threadcount">
    <title>gp_fts_probe_threadcount</title>
    <body>
      <p>Specifies the number of <codeph>ftsprobe</codeph> threads to create. This parameter should
        be set to a value equal to or greater than the number of segments per host. </p>
      <table id="gp_fts_probe_threadcount_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">1 - 128</entry>
              <entry colname="col2">16</entry>
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_fts_probe_timeout">
    <title>gp_fts_probe_timeout</title>
    <body>
      <p>Specifies the allowed timeout for the fault detection process (<codeph>ftsprobe</codeph>)
        to establish a connection to a segment before declaring it down. </p>
      <table id="gp_fts_probe_timeout_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">10 - 3600 seconds</entry>
              <entry colname="col2">20 secs</entry>
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
L
docs - discuss the global deadlock detector (#6538)  
Lisa Owen 已提交
3361 3362 3363 
  <topic id="gp_global_deadlock_detector_period">
    <title>gp_global_deadlock_detector_period</title>
    <body>
M
docs - minor change. GDD "backend" to "background worker" (#8225)  
Mel Kiyama 已提交
3364 3365 
      <p>Specifies the executing interval (in seconds) of the global deadlock detector background
        worker process.</p>
L
docs - discuss the global deadlock detector (#6538)  
Lisa Owen 已提交
3366 3367 3368 3369 3370 3371 3372 3373 3374 3375 3376 3377 3378 3379 3380 3381 3382 3383 3384 3385 3386 3387 3388 
      <table id="gp_global_deadlock_detector_period">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">5 - <codeph>INT_MAX</codeph> secs</entry>
              <entry colname="col2">120 secs</entry>
              <entry colname="col3">master<p>system</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
3389 3390 3391 3392 3393 3394 3395 3396 3397 3398 3399 3400 3401 3402 3403 3404 3405 3406 3407 3408 3409 3410 3411 3412 3413 3414 3415 3416 
  <topic id="gp_log_fts">
    <title>gp_log_fts</title>
    <body>
      <p>Controls the amount of detail the fault detection process (<codeph>ftsprobe</codeph>)
        writes to the log file. </p>
      <table id="gp_log_fts_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">OFF<p>TERSE</p><p>VERBOSE</p><p>DEBUG</p></entry>
              <entry colname="col2">TERSE</entry>
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
M
DOCS: gucs for interconnect debugging (#3068)  
Mel Kiyama 已提交
3417 3418 3419 3420 3421 3422 3423 3424 3425 3426 3427 3428 3429 3430 3431 3432 3433 3434 3435 3436 3437 3438 3439 3440 3441 3442 3443 3444 3445 3446 3447 3448 3449 3450 3451 3452 3453 
  <topic id="gp_log_interconnect">
    <title>gp_log_interconnect</title>
    <body>
      <p>Controls the amount of information that is written to the log file about communication
        between Greenplum Database segment instance worker processes. The default value is
          <codeph>terse</codeph>. The log information is written to both the master and segment
        instance logs.</p>
      <p>Increasing the amount of logging could affect performance and increase disk space
        usage.</p>
      <table id="table_xkm_nqr_y1b">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">
                <p>off</p>
                <p>terse</p>
                <p>verbose</p>
                <p>debug</p>
              </entry>
              <entry colname="col2">terse</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
M
GPDB DOCS - new GUCs from 4.3.x and mdcache (#2518)  
mkiyama 已提交
3454 3455 3456 3457 3458 3459 3460 3461 3462 3463 3464 3465 3466 3467 3468 3469 3470 3471 3472 3473 3474 3475 3476 3477 3478 3479 3480 3481 3482 
  <topic id="gp_log_gang">
    <title>gp_log_gang</title>
    <body>
      <p>Controls the amount of information that is written to the log file about query worker
        process creation and query management. The default value is <codeph>OFF</codeph>, do not log
        information.</p>
      <table id="gp_log_fts_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">OFF<p>TERSE</p><p>VERBOSE</p><p>DEBUG</p></entry>
              <entry colname="col2">OFF</entry>
              <entry colname="col3">master<p>session</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
3483 3484 3485 3486 
  <topic id="gp_gpperfmon_send_interval">
    <title>gp_gpperfmon_send_interval</title>
    <body>
      <p>Sets the frequency that the Greenplum Database server processes send query execution
M
GPDB DOCS update set classifications for GUC standard_conforming_strings  
mkiyama 已提交
3487 
        updates to the data collection agent processes used to populate the
C
docs - GPCC no longer depends on gpperfmon_install (#7972)  
Chuck Litzell 已提交
3488 
          <codeph>gpperfmon</codeph> database. Query operations executed during
M
doc fix- pljava_classpath_insecure GUC - requires restart not reload  
mkiyama 已提交
3489 3490 3491 
        this interval are sent through UDP to the segment monitor agents. If you find that an
        excessive number of UDP packets are dropped during long-running, complex queries, you may
        consider increasing this value.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
3492 3493 3494 3495 3496 3497 3498 3499 3500 3501 3502 3503 3504 3505 3506 3507 
      <table id="gp_gpperfmon_send_interval_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Any valid time expression (number and unit)</entry>
              <entry colname="col2">1sec</entry>
M
docs - add superuser to gp_gpperfmon_send_interval GUC set classifications (#8407)  
Mel Kiyama 已提交
3508 
              <entry colname="col3">master<p>system</p><p>restart</p><p>superuser</p></entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
3509 3510 3511 3512 3513 3514 3515 3516 3517 3518 3519 
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gpperfmon_log_alert_level">
    <title>gpperfmon_log_alert_level</title>
    <body>
      <p>Controls which message levels are written to the gpperfmon log. Each level includes all the
        levels that follow it. The later the level, the fewer messages are sent to the log. </p>
C
Relocates gpperfmon reference from GPCC (#2388)  
Chuck Litzell 已提交
3520 
      <note>If the <codeph>gpperfmon</codeph> database is installed and is monitoring the database,
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
3521 3522 3523 3524 3525 3526 3527 3528 3529 3530 3531 3532 3533 3534 3535 3536 3537 3538 3539 3540 3541 3542 3543 3544 3545 3546 3547 3548 3549 3550 3551 3552 3553 3554 3555 3556 3557 3558 3559 3560 3561 3562 3563 3564 3565 3566 3567 3568 3569 3570 3571 3572 
        the default value is warning.</note>
      <table id="gpperfmon_log_alert_level_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">none <p>warning</p><p>error</p><p>fatal</p><p>panic</p></entry>
              <entry colname="col2">none</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_hashjoin_tuples_per_bucket">
    <title>gp_hashjoin_tuples_per_bucket</title>
    <body>
      <p>Sets the target density of the hash table used by HashJoin operations. A smaller value will
        tend to produce larger hash tables, which can increase join performance.</p>
      <table id="gp_hashjoin_tuples_per_bucket_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
              <entry colname="col2">5</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
M
docs: add GUC gp_ignore_error_table (#4628)  
Mel Kiyama 已提交
3573 
  <topic id="gp_ignore_error_table">
D
Mark gp_ignore_error_table as deprecated  
Daniel Gustafsson 已提交
3574 
    <title>gp_ignore_error_table (Deprecated)</title>
M
docs: add GUC gp_ignore_error_table (#4628)  
Mel Kiyama 已提交
3575 
    <body>
M
docs - add GUC gp_enable_global_deadlock_detector (#6894)  
Mel Kiyama 已提交
3576 3577 3578 
      <p>Controls Greenplum Database behavior when the deprecated <codeph>INTO ERROR TABLE</codeph>
        clause is specified in a <codeph>CREATE EXTERNAL TABLE</codeph> or <codeph>COPY</codeph>
        command.</p>
M
docs: add GUC gp_ignore_error_table (#4628)  
Mel Kiyama 已提交
3579 3580 3581 
      <p>The default value is <codeph>false</codeph>, Greenplum Database returns an error if the
          <codeph>INTO ERROR TABLE</codeph> clause is specified in a command. </p>
      <p>If the value is <codeph>true</codeph>, Greenplum Database ignores the clause, issues a
M
docs - update GUC gp_ignore_error_table (#5135)  
Mel Kiyama 已提交
3582 3583 
        warning, and executes the command without the <codeph>INTO ERROR TABLE</codeph> clause. In
        Greenplum Database 5.x and later, you access the error log information with built-in SQL
M
docs: add GUC gp_ignore_error_table (#4628)  
Mel Kiyama 已提交
3584 3585 3586 
        functions. See the <codeph><xref href="../sql_commands/CREATE_EXTERNAL_TABLE.xml">CREATE
            EXTERNAL TABLE</xref></codeph> or <codeph><xref href="../sql_commands/COPY.xml"
            >COPY</xref></codeph> command.</p>
M
docs - update GUC gp_ignore_error_table (#5135)  
Mel Kiyama 已提交
3587 3588 
      <p>You can set this value to <codeph>true</codeph> to avoid the Greenplum Database error when
        you run applications that execute <codeph>CREATE EXTERNAL TABLE</codeph> or
M
docs: add GUC gp_ignore_error_table (#4628)  
Mel Kiyama 已提交
3589 3590 
          <codeph>COPY</codeph> commands that include the Greenplum Database 4.3.x <codeph>INTO
          ERROR TABLE</codeph> clause.</p>
M
docs - add GUC gp_enable_global_deadlock_detector (#6894)  
Mel Kiyama 已提交
3591 3592 3593 
      <p>The <codeph>INTO ERROR TABLE</codeph> clause was deprecated and removed in Greenplum
        Database 5. In Greenplum Database 7, this parameter will be removed as well, causing all
          <codeph>INTO ERROR TABLE</codeph> invocations be yield a syntax error.</p>
M
docs: add GUC gp_ignore_error_table (#4628)  
Mel Kiyama 已提交
3594 3595 3596 3597 3598 3599 3600 3601 3602 3603 3604 3605 3606 3607 3608 3609 
      <table id="table_hnf_2v5_bdb">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">false</entry>
M
docs - update GUC gp_ignore_error_table (#5135)  
Mel Kiyama 已提交
3610 
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
M
docs: add GUC gp_ignore_error_table (#4628)  
Mel Kiyama 已提交
3611 3612 3613 3614 3615 3616 
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
3617 3618 3619 3620 3621 3622 3623 3624 3625 3626 3627 3628 3629 3630 3631 3632 3633 3634 3635 3636 3637 3638 3639 3640 3641 3642 3643 3644 3645 3646 3647 3648 3649 3650 3651 3652 
  <topic id="topic_lvm_ttc_3p">
    <title>gp_initial_bad_row_limit</title>
    <body>
      <p>For the parameter value <i>n</i>, Greenplum Database stops processing input rows when you
        import data with the <codeph>COPY</codeph> command or from an external table if the first
          <i>n</i> rows processed contain formatting errors. If a valid row is processed within the
        first <i>n</i> rows, Greenplum Database continues processing input rows.</p>
      <p>Setting the value to 0 disables this limit. </p>
      <p>The <codeph>SEGMENT REJECT LIMIT</codeph> clause can also be specified for the
          <codeph>COPY</codeph> command or the external table definition to limit the number of
        rejected rows. </p>
      <p>
        <codeph>INT_MAX</codeph> is the largest value that can be stored as an integer on your
        system.</p>
      <table id="gp_initial_bad_row_limit">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer 0 - <codeph>INT_MAX</codeph></entry>
              <entry colname="col2">1000</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
M
DOCS: gucs for interconnect debugging (#3068)  
Mel Kiyama 已提交
3653 
  </topic>
C
docs: add real-time query metrics GUCs to reference (#4618)  
Chuck Litzell 已提交
3654 3655 3656 
  <topic id="gp_instrument_shmem_size">
    <title>gp_instrument_shmem_size</title>
    <body>
M
docs: add guc gp_max_slices (#4854)  
Mel Kiyama 已提交
3657 3658 3659 3660 3661 3662 3663 3664 3665 3666 
      <p>The amount of shared memory, in kilobytes, allocated for query metrics. The default is 5120
        and the maximum is 131072. At startup, if <codeph><xref href="#gp_enable_query_metrics"
            format="dita">gp_enable_query_metrics</xref></codeph> is set to on, Greenplum Database
        allocates space in shared memory to save query metrics. This memory is organized as a header
        and a list of slots. The number of slots needed depends on the number of concurrent queries
        and the number of execution plan nodes per query. The default value, 5120, is based on a
        Greenplum Database system that executes a maximum of about 250 concurrent queries with 120
        nodes per query. If the <codeph>gp_enable_query_metrics</codeph> configuration parameter is
        off, or if the slots are exhausted, the metrics are maintained in local memory instead of in
        shared memory. </p>
C
docs: add real-time query metrics GUCs to reference (#4618)  
Chuck Litzell 已提交
3667 3668 3669 3670 3671 3672 3673 3674 3675 3676 3677 3678 3679 3680 3681 3682 
      <table id="gp_instrument_shmem_size">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer <codeph>0 - 131072</codeph></entry>
              <entry colname="col2">5120</entry>
M
docs: add guc gp_max_slices (#4854)  
Mel Kiyama 已提交
3683 3684 
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
C
docs: add real-time query metrics GUCs to reference (#4618)  
Chuck Litzell 已提交
3685 3686 3687 3688 3689 
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
M
DOCS: gucs for interconnect debugging (#3068)  
Mel Kiyama 已提交
3690 3691 3692 3693 3694 3695 3696 3697 3698 3699 3700 3701 3702 3703 3704 3705 3706 3707 3708 3709 3710 3711 3712 3713 3714 3715 3716 3717 3718 3719 3720 3721 
  <topic id="gp_interconnect_debug_retry_interval">
    <title>gp_interconnect_debug_retry_interval</title>
    <body>
      <p>Specifies the interval, in seconds, to log Greenplum Database interconnect debugging
        messages when the server configuration parameter <codeph><xref href="#gp_log_interconnect"
            format="dita">gp_log_interconnect</xref></codeph> is set to <codeph>DEBUG</codeph>. The
        default is 10 seconds. </p>
      <p>The log messages contain information about the interconnect communication between Greenplum
        Database segment instance worker processes. The information can be helpful when debugging
        network issues between segment instances.</p>
      <table id="table_q1n_v4r_y1b">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">1 =&lt; Integer &lt; 4096</entry>
              <entry colname="col2">10</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
3722 3723 3724 3725 
  </topic>
  <topic id="gp_interconnect_fc_method">
    <title>gp_interconnect_fc_method</title>
    <body>
D
removing/rewording interconnect docs as only UDPIFC is supported in 5… (#2387)  
David Yozie 已提交
3726 3727 
      <p>Specifies the flow control method used for the default Greenplum Database UDPIFC
        interconnect.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
3728 3729 3730 3731 3732 3733 3734 3735 3736 3737 3738 3739 3740 3741 3742 3743 3744 3745 3746 3747 3748 3749 3750 3751 3752 3753 3754 3755 3756 3757 
      <p>For capacity based flow control, senders do not send packets when receivers do not have the
        capacity.</p>
      <p>Loss based flow control is based on capacity based flow control, and also tunes the sending
        speed according to packet losses.</p>
      <table id="gp_interconnect_fc_method_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">CAPACITY<p>LOSS</p></entry>
              <entry colname="col2">LOSS</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_interconnect_queue_depth">
    <title>gp_interconnect_queue_depth</title>
    <body>
D
removing/rewording interconnect docs as only UDPIFC is supported in 5… (#2387)  
David Yozie 已提交
3758 3759 3760 3761 3762 3763 3764 
      <p>Sets the amount of data per-peer to be queued by the Greenplum Database interconnect on
        receivers (when data is received but no space is available to receive it the data will be
        dropped, and the transmitter will need to resend it) for the default UDPIFC interconnect.
        Increasing the depth from its default value will cause the system to use more memory, but
        may increase performance. It is reasonable to set this value between 1 and 10. Queries with
        data skew potentially perform better with an increased queue depth. Increasing this may
        radically increase the amount of memory used by the system.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
3765 3766 3767 3768 3769 3770 3771 3772 3773 3774 3775 3776 3777 3778 3779 3780 3781 3782 3783 3784 3785 3786 3787 3788 3789 3790 
      <table id="gp_interconnect_queue_depth_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">1-2048</entry>
              <entry colname="col2">4</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_interconnect_setup_timeout">
    <title>gp_interconnect_setup_timeout</title>
    <body>
M
GPDB DOCS - new GUCs from 4.3.x and mdcache (#2518)  
mkiyama 已提交
3791 3792 
      <p>Specifies the amount of time to wait for the Greenplum Database interconnect to complete
        setup before it times out.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
3793 3794 3795 3796 3797 3798 3799 3800 3801 3802 3803 3804 3805 3806 3807 3808 3809 3810 3811 3812 3813 3814 3815 3816 3817 3818 
      <table id="gp_interconnect_setup_timeout_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Any valid time expression (number and unit)</entry>
              <entry colname="col2">2 hours</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_interconnect_snd_queue_depth">
    <title>gp_interconnect_snd_queue_depth</title>
    <body>
D
removing/rewording interconnect docs as only UDPIFC is supported in 5… (#2387)  
David Yozie 已提交
3819 3820 3821 3822 3823 
      <p>Sets the amount of data per-peer to be queued by the default UDPIFC interconnect on
        senders. Increasing the depth from its default value will cause the system to use more
        memory, but may increase performance. Reasonable values for this parameter are between 1 and
        4. Increasing the value might radically increase the amount of memory used by the
        system.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
3824 3825 3826 3827 3828 3829 3830 3831 3832 3833 3834 3835 3836 3837 3838 3839 3840 3841 3842 3843 3844 3845 3846 3847 3848 3849 
      <table id="gp_interconnect_snd_queue_depth_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">1 - 4096</entry>
              <entry colname="col2">2 </entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_interconnect_type">
    <title>gp_interconnect_type</title>
    <body>
D
removing/rewording interconnect docs as only UDPIFC is supported in 5… (#2387)  
David Yozie 已提交
3850 3851 3852 
      <p>Sets the networking protocol used for Greenplum Database interconnect traffic. UDPIFC
        specifies using UDP with flow control for interconnect traffic, and is the only value
        supported.</p>
M
GPDB DOCS update set classifications for GUC standard_conforming_strings  
mkiyama 已提交
3853 3854 3855 3856 3857 3858 
      <p>UDPIFC (the default) specifies using UDP with flow control for interconnect traffic.
        Specify the interconnect flow control method with <xref href="#gp_interconnect_fc_method"
          format="dita"/>.</p>
      <p>With TCP as the interconnect protocol, Greenplum Database has an upper limit of 1000
        segment instances - less than that if the query workload involves complex, multi-slice
        queries.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
3859 3860 3861 3862 3863 3864 3865 3866 3867 3868 3869 3870 3871 3872 
      <table id="table_jn5_frn_xv">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
D
removing/rewording interconnect docs as only UDPIFC is supported in 5… (#2387)  
David Yozie 已提交
3873 
              <entry colname="col1">UDPIFC<p>TCP</p></entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
3874 3875 3876 3877 3878 3879 3880 3881 3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 3899 3900 3901 3902 3903 3904 3905 3906 3907 3908 3909 3910 3911 3912 3913 3914 3915 3916 3917 3918 3919 3920 3921 3922 3923 3924 3925 3926 3927 3928 3929 3930 3931 3932 3933 3934 3935 3936 3937 3938 3939 3940 3941 3942 3943 3944 3945 3946 
              <entry colname="col2">UDPIFC</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_log_format">
    <title>gp_log_format</title>
    <body>
      <p>Specifies the format of the server log files. If using <i>gp_toolkit</i> administrative
        schema, the log files must be in CSV format.</p>
      <table id="gp_log_format_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">csv<p>text</p></entry>
              <entry colname="col2">csv</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_max_local_distributed_cache">
    <title>gp_max_local_distributed_cache</title>
    <body>
      <p>Sets the maximum number of distributed transaction log entries to cache in the backend
        process memory of a segment instance. </p>
      <p>The log entries contain information about the state of rows that are being accessed by an
        SQL statement. The information is used to determine which rows are visible to an SQL
        transaction when executing multiple simultaneous SQL statements in an MVCC environment.
        Caching distributed transaction log entries locally improves transaction processing speed by
        improving performance of the row visibility determination process.</p>
      <p>The default value is optimal for a wide variety of SQL processing environments. </p>
      <table id="gp_max_local_distributed_cache_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
              <entry colname="col2">1024</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_max_packet_size">
    <title>gp_max_packet_size</title>
    <body>
M
GPDB DOCS - new GUCs from 4.3.x and mdcache (#2518)  
mkiyama 已提交
3947 
      <p>Sets the tuple-serialization chunk size for the Greenplum Database interconnect.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
3948 3949 3950 3951 3952 3953 3954 3955 3956 3957 3958 3959 3960 3961 3962 3963 3964 3965 3966 3967 3968 3969 3970 3971 3972 3973 3974 3975 3976 3977 3978 3979 3980 3981 3982 3983 3984 3985 3986 3987 3988 3989 3990 3991 3992 3993 3994 3995 3996 3997 3998 3999 4000 4001 4002 4003 4004 
      <table id="gp_max_packet_size_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">512-65536</entry>
              <entry colname="col2">8192</entry>
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_max_plan_size">
    <title>gp_max_plan_size</title>
    <body>
      <p>Specifies the total maximum uncompressed size of a query execution plan multiplied by the
        number of Motion operators (slices) in the plan. If the size of the query plan exceeds the
        value, the query is cancelled and an error is returned. A value of 0 means that the size of
        the plan is not monitored.</p>
      <p>You can specify a value in <codeph>kB</codeph>, <codeph>MB</codeph>, or
        <codeph>GB</codeph>. The default unit is <codeph>kB</codeph>. For example, a value of
          <codeph>200</codeph> is 200kB. A value of <codeph>1GB</codeph> is the same as
          <codeph>1024MB</codeph> or <codeph>1048576kB</codeph>.</p>
      <table id="gp_max_plan_size_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
              <entry colname="col2">0</entry>
              <entry colname="col3">master<p>superuser</p><p>session</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
M
docs: add guc gp_max_slices (#4854)  
Mel Kiyama 已提交
4005 4006 4007 4008 4009 4010 4011 4012 4013 4014 4015 4016 4017 4018 4019 4020 4021 4022 4023 4024 4025 4026 4027 4028 4029 4030 4031 4032 4033 4034 4035 4036 4037 4038 4039 
  <topic id="gp_max_slices">
    <title>gp_max_slices</title>
    <body>
      <p dir="ltr">Specifies the maximum number of slices (portions of a query plan that are
        executed on segment instances) that can be generated by a query. If the query generates more
        than the specified number of slices, Greenplum Database returns an error and does not
        execute the query. The default value is <codeph>0</codeph>, no maximum value. </p>
      <p>Executing a query that generates a large number of slices might affect Greenplum Database
        performance. For example, a query that contains <codeph>UNION</codeph> or <codeph>UNION
          ALL</codeph> operators over several complex views can generate a large number of slices.
        You can run <codeph>EXPLAIN ANALYZE</codeph> on the query to view slice statistics for the
        query.</p>
      <table id="table_uwf_lzw_ldb">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">0 - INT_MAX</entry>
              <entry colname="col2">0</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
4040 4041 4042 
  <topic id="gp_motion_cost_per_row">
    <title>gp_motion_cost_per_row</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
4043 
      <p>Sets the Postgres Planner cost estimate for a Motion operator to transfer a
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
4044 4045 4046 4047 4048 4049 4050 4051 4052 4053 4054 4055 4056 4057 4058 4059 4060 4061 4062 4063 4064 4065 4066 4067 4068 
        row from one segment to another, measured as a fraction of the cost of a sequential page
        fetch. If 0, then the value used is two times the value of <i>cpu_tuple_cost</i>.</p>
      <table id="gp_motion_cost_per_row_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">floating point</entry>
              <entry colname="col2">0</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Rename recursive CTE guc to remove _prototype  
Daniel Gustafsson 已提交
4069 4070 
  <topic id="gp_recursive_cte">
    <title>gp_recursive_cte</title>
M
DOCS: SELECT/ SELECT INTO - Add RECURSIVE keyword to WITH clause (#2989)  
Mel Kiyama 已提交
4071 
    <body>
D
Update docs for gp_recursive_cte enabled by default  
Daniel Gustafsson 已提交
4072 
      <p>Controls the availability of the <codeph>RECURSIVE</codeph> keyword in the
M
docs - CTE available with INSERT, UPDATE, DELETE (#7025)  
Mel Kiyama 已提交
4073 4074 4075 4076 4077 4078 4079 4080 
          <codeph>WITH</codeph> clause of a <codeph>SELECT [INTO]</codeph> command, or a
          <codeph>DELETE</codeph>, <codeph>INSERT</codeph> or <codeph>UPDATE</codeph> command. The
        keyword allows a subquery in the <codeph>WITH</codeph> clause of a command to reference
        itself. The default value is <codeph>false</codeph>, the <codeph>RECURSIVE</codeph> keyword
        is not allowed in the <codeph>WITH</codeph> clause of a command.</p>
      <p>For information about the <codeph>RECURSIVE</codeph> keyword (Beta), see the
            <codeph><xref href="../sql_commands/SELECT.xml">SELECT</xref></codeph> command and <xref
          href="../../admin_guide/query/topics/CTE-query.xml"/>.</p>
M
DOCS: SELECT/ SELECT INTO - Add RECURSIVE keyword to WITH clause (#2989)  
Mel Kiyama 已提交
4081 4082 
      <p>The parameter can be set for a database system, an individual database, or a session or
        query.</p>
D
Update docs for gp_recursive_cte enabled by default  
Daniel Gustafsson 已提交
4083 
      <note>This parameter was previously named <codeph>gp_recursive_cte_prototype</codeph>, but
D
Rename recursive CTE guc to remove _prototype  
Daniel Gustafsson 已提交
4084 
        has been renamed to reflect the current status of the implementation.</note>
M
DOCS: SELECT/ SELECT INTO - Add RECURSIVE keyword to WITH clause (#2989)  
Mel Kiyama 已提交
4085 4086 4087 4088 4089 4090 4091 4092 4093 4094 4095 4096 4097 4098 4099 
      <table id="table_j4s_yyx_1bb">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
D
Update docs for gp_recursive_cte enabled by default  
Daniel Gustafsson 已提交
4100 
              <entry colname="col2">true</entry>
M
DOCS: SELECT/ SELECT INTO - Add RECURSIVE keyword to WITH clause (#2989)  
Mel Kiyama 已提交
4101 4102 4103 4104 4105 4106 4107 
              <entry colname="col3">master<p>session</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
4108 4109 4110 4111 4112 4113 4114 4115 4116 4117 4118 4119 4120 4121 4122 4123 4124 4125 4126 4127 4128 4129 4130 4131 4132 4133 4134 4135 4136 4137 4138 4139 4140 4141 4142 4143 4144 4145 4146 4147 4148 4149 4150 4151 4152 4153 4154 4155 4156 4157 4158 
  <topic id="gp_reject_percent_threshold">
    <title>gp_reject_percent_threshold</title>
    <body>
      <p>For single row error handling on COPY and external table SELECTs, sets the number of rows
        processed before SEGMENT REJECT LIMIT <i>n</i> PERCENT starts calculating.</p>
      <table id="gp_reject_percent_threshold_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">1-<i>n</i></entry>
              <entry colname="col2">300</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_reraise_signal">
    <title>gp_reraise_signal</title>
    <body>
      <p>If enabled, will attempt to dump core if a fatal server error occurs.</p>
      <table id="gp_reraise_signal_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
L
docs - resgroup gp_resgroup_memory_policy GUC, show/set limit bypass (#3514)  
Lisa Owen 已提交
4159 4160 4161 4162 4163 4164 4165 
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_resgroup_memory_policy">
    <title>gp_resgroup_memory_policy</title>
    <body>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
4166 4167 
      <note>The <codeph>gp_resgroup_memory_policy</codeph> server configuration parameter is
        enforced only when resource group-based resource management is active.</note>
L
docs - resgroup gp_resgroup_memory_policy GUC, show/set limit bypass (#3514)  
Lisa Owen 已提交
4168 
      <p>Used by a resource group to manage memory allocation to query operators.</p>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
4169 4170 4171 4172 4173 4174 
      <p>When set to <codeph>auto</codeph>, Greenplum Database uses resource group memory limits to
        distribute memory across query operators, allocating a fixed size of memory to
        non-memory-intensive operators and the rest to memory-intensive operators.</p>
      <p>When you specify <codeph>eager_free</codeph>, Greenplum Database distributes memory among
        operators more optimally by re-allocating memory released by operators that have completed
        their processing to operators in a later query stage.</p>
L
docs - resgroup gp_resgroup_memory_policy GUC, show/set limit bypass (#3514)  
Lisa Owen 已提交
4175 4176 4177 4178 4179 4180 4181 4182 4183 4184 4185 4186 4187 4188 4189 4190 4191 4192 4193 
      <table id="gp_resgroup_memory_policy_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">auto, eager_free</entry>
              <entry colname="col2">eager_free</entry>
              <entry colname="col3">local<p>system</p><p>superuser</p><p>restart/reload</p></entry>
            </row>
          </tbody>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
4194 4195 4196 4197 
        </tgroup>
      </table>
    </body>
  </topic>
M
docs - add GUC gp_resource_group_bypass (#5231)  
Mel Kiyama 已提交
4198 4199 4200 4201 4202 4203 4204 4205 4206 4207 4208 4209 4210 4211 4212 4213 4214 4215 
  <topic id="gp_resource_group_bypass">
    <title>gp_resource_group_bypass</title>
    <body>
      <note>The <codeph>gp_resource_group_bypass</codeph> server configuration parameter is enforced
        only when resource group-based resource management is active.</note>
      <p>Enables or disables the enforcement of resource group concurrent transaction limits on
        Greenplum Database resources. The default value is <codeph>false</codeph>, which enforces
        resource group transaction limits. Resource groups manage resources such as CPU, memory, and
        the number of concurrent transactions that are used by queries and external components such
        as PL/Container. </p>
      <p>You can set this parameter to <codeph>true</codeph> to bypass resource group concurrent
        transaction limitations so that a query can run immediately. For example, you can set the
        parameter to <codeph>true</codeph> for a session to run a system catalog query or a similar
        query that requires a minimal amount of resources. </p>
      <p>When you set this parameter to <codeph>true</codeph> and a run a query, the query runs in
        this environment:<ul id="ul_vgc_rw4_j2b">
          <li>The query runs inside a resource group. The resource group assignment for the query
            does not change.</li>
M
docs - minor edit to gp_resource_group_bypass GUC base on release note review  
mkiyama 已提交
4216 4217 4218 
          <li>The query memory quota is approximately 10 MB per query. The memory is allocated from
            resource group shared memory or global shared memory. The query fails if there is not
            enough shared memory available to fulfill the memory allocation request.</li>
M
docs - add GUC gp_resource_group_bypass (#5231)  
Mel Kiyama 已提交
4219 4220 4221 4222 4223 4224 4225 4226 4227 4228 4229 4230 4231 4232 4233 4234 4235 4236 4237 4238 4239 4240 4241 4242 4243 4244 
        </ul></p>
      <p>This parameter can be set for a session. The parameter cannot be set within a transaction
        or a function.</p>
      <table id="table_szz_1yt_32b">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">false</entry>
              <entry colname="col3">session</entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
L
docs - add some resource group GUCs to the reference guide (#2926)  
Lisa Owen 已提交
4245 4246 4247 
  <topic id="gp_resource_group_cpu_limit">
    <title>gp_resource_group_cpu_limit</title>
    <body>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
4248 4249 
      <note>The <codeph>gp_resource_group_cpu_limit</codeph> server configuration parameter is
        enforced only when resource group-based resource management is active.</note>
M
DOCS: update gpconfig. Updated, simplified quoting syntax for GUC values (#3016)  
Mel Kiyama 已提交
4250 4251 
      <p>Identifies the maximum percentage of system CPU resources to allocate to resource groups on
        each Greenplum Database segment node.</p>
L
docs - add some resource group GUCs to the reference guide (#2926)  
Lisa Owen 已提交
4252 4253 4254 4255 4256 4257 4258 4259 4260 4261 4262 4263 4264 4265 4266 4267 4268 4269 4270 4271 4272 4273 4274 4275 4276 4277 
      <table id="gp_resource_group_cpu_limit_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">0.1 - 1.0</entry>
              <entry colname="col2">0.9</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_resource_group_memory_limit">
    <title>gp_resource_group_memory_limit</title>
    <body>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
4278 4279 
      <note>The <codeph>gp_resource_group_memory_limit</codeph> server configuration parameter is
        enforced only when resource group-based resource management is active.</note>
M
DOCS: update gpconfig. Updated, simplified quoting syntax for GUC values (#3016)  
Mel Kiyama 已提交
4280 4281 
      <p>Identifies the maximum percentage of system memory resources to allocate to resource groups
        on each Greenplum Database segment node.</p>
L
docs - add some resource group GUCs to the reference guide (#2926)  
Lisa Owen 已提交
4282 4283 4284 4285 4286 4287 4288 4289 4290 4291 4292 4293 4294 4295 4296 
      <table id="gp_resource_group_memory_limit_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">0.1 - 1.0</entry>
L
docs - gp_resource_group_memory_limit default is .7 (#3717)  
Lisa Owen 已提交
4297 
              <entry colname="col2">0.7</entry>
L
docs - add some resource group GUCs to the reference guide (#2926)  
Lisa Owen 已提交
4298 4299 4300 4301 4302 
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
4303 4304 4305 4306 4307 4308 4309 4310 4311 4312 4313 4314 4315 
      <note>When resource group-based resource management is active, the memory allotted to a
        segment host is equally shared by active primary segments. Greenplum Database assigns memory
        to primary segments when the segment takes the primary role. The initial memory allotment to
        a primary segment does not change, even in a failover situation. This may result in a
        segment host utilizing more memory than the <codeph>gp_resource_group_memory_limit</codeph>
        setting permits. <p>For example, suppose your Greenplum Database cluster is utilizing the
          default <codeph>gp_resource_group_memory_limit</codeph> of <codeph>0.7</codeph> and a
          segment host named <codeph>seghost1</codeph> has 4 primary segments and 4 mirror segments.
          Greenplum Database assigns each primary segment on <codeph>seghost1</codeph>
          <codeph>(0.7 / 4 = 0.175%)</codeph> of overall system memory. If failover occurs and two
          mirrors on <codeph>seghost1</codeph> fail over to become primary segments, each of the
          original 4 primaries retain their memory allotment of <codeph>0.175</codeph>, and the two
          new primary segments are each allotted <codeph>(0.7 / 6 = 0.116%)</codeph> of system
M
docs - remove track_count GUC for pg_stat_* and pg_statio_* views (#6479)  
Mel Kiyama 已提交
4316 4317 4318 4319 
          memory. <codeph>seghost1</codeph>'s overall memory allocation in this scenario is</p><p>
          <codeblock>
0.7 + (0.116 * 2) = 0.932%</codeblock>
        </p>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
4320 4321 
        <p>which is above the percentage configured in the
            <codeph>gp_resource_group_memory_limit</codeph> setting.</p></note>
L
docs - add some resource group GUCs to the reference guide (#2926)  
Lisa Owen 已提交
4322 4323 4324 4325 4326 
    </body>
  </topic>
  <topic id="gp_resource_manager">
    <title>gp_resource_manager</title>
    <body>
M
DOCS: update gpconfig. Updated, simplified quoting syntax for GUC values (#3016)  
Mel Kiyama 已提交
4327 
      <p>Identifies the resource management scheme currently enabled in the Greenplum Database
D
Edits to make 'resource management' using resource queues, resources … (#3353)  
David Yozie 已提交
4328 
        cluster. The default scheme is to use resource queues.</p>
L
docs - add some resource group GUCs to the reference guide (#2926)  
Lisa Owen 已提交
4329 4330 4331 4332 4333 4334 4335 4336 4337 4338 4339 4340 4341 4342 4343 4344 4345 4346 4347 4348 4349 4350 4351 
      <table id="gp_resource_manager_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">group <p>queue</p></entry>
              <entry colname="col2">queue</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
4352 4353 4354 
  <topic id="gp_resqueue_memory_policy">
    <title>gp_resqueue_memory_policy</title>
    <body>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
4355 4356 
      <note>The <codeph>gp_resqueue_memory_policy</codeph> server configuration parameter is
        enforced only when resource queue-based resource management is active.</note>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
4357 4358 4359 4360 4361 4362 4363 4364 4365 4366 4367 4368 4369 4370 4371 4372 4373 4374 4375 4376 4377 4378 4379 4380 4381 4382 4383 4384 4385 4386 4387 4388 4389 4390 4391 
      <p>Enables Greenplum memory management features. The distribution algorithm
          <codeph>eager_free</codeph> takes advantage of the fact that not all operators execute at
        the same time<ph> (in Greenplum Database 4.2 and later)</ph>. The query plan is divided into
        stages and Greenplum Database eagerly frees memory allocated to a previous stage at the end
        of that stage's execution, then allocates the eagerly freed memory to the new stage. </p>
      <p>When set to <codeph>none</codeph>, memory management is the same as in Greenplum Database
        releases prior to 4.1. </p>
      <p>When set to <codeph>auto</codeph>, query memory usage is controlled by <xref
          href="#statement_mem" format="dita"/> and resource queue memory limits. </p>
      <table id="gp_resqueue_memory_policy_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">none, auto, eager_free</entry>
              <entry colname="col2">eager_free</entry>
              <entry colname="col3">local<p>system</p><p>restart/reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_resqueue_priority">
    <title>gp_resqueue_priority</title>
    <body>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
4392 4393 
      <note>The <codeph>gp_resqueue_priority</codeph> server configuration parameter is enforced
        only when resource queue-based resource management is active.</note>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
4394 4395 4396 4397 4398 4399 4400 4401 4402 4403 4404 4405 4406 4407 4408 4409 4410 4411 4412 4413 4414 4415 4416 4417 4418 4419 4420 4421 
      <p>Enables or disables query prioritization. When this parameter is disabled, existing
        priority settings are not evaluated at query run time.</p>
      <table id="gp_resqueue_priority_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_resqueue_priority_cpucores_per_segment">
    <title>gp_resqueue_priority_cpucores_per_segment</title>
    <body>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
4422 4423 
      <note>The <codeph>gp_resqueue_priority_cpucores_per_segment</codeph> server configuration
        parameter is enforced only when resource queue-based resource management is active.</note>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
4424 4425 4426 4427 4428 4429 4430 4431 4432 4433 4434 4435 4436 4437 4438 4439 4440 4441 4442 4443 4444 4445 4446 4447 4448 4449 4450 4451 4452 4453 4454 4455 4456 
      <p>Specifies the number of CPU units allocated per segment instance. For example, if a
        Greenplum Database cluster has 10-core segment hosts that are configured with four segments,
        set the value for the segment instances to 2.5. For the master instance, the value would be
        10. A master host typically has only the master instance running on it, so the value for the
        master should reflect the usage of all available CPU cores. </p>
      <p>Incorrect settings can result in CPU under-utilization or query prioritization not working
        as designed. </p>
      <table id="gp_resqueue_priority_cpucores_per_segment_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">0.1 - 512.0</entry>
              <entry colname="col2">4</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_resqueue_priority_sweeper_interval">
    <title>gp_resqueue_priority_sweeper_interval</title>
    <body>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
4457 4458 
      <note>The <codeph>gp_resqueue_priority_sweeper_interval</codeph> server configuration
        parameter is enforced only when resource queue-based resource management is active.</note>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
4459 4460 4461 4462 4463 4464 4465 4466 4467 4468 4469 4470 4471 4472 4473 4474 4475 4476 4477 4478 4479 4480 4481 4482 4483 4484 4485 4486 4487 4488 4489 4490 4491 4492 4493 4494 4495 4496 4497 4498 4499 4500 4501 4502 4503 4504 4505 4506 4507 4508 4509 4510 4511 4512 4513 4514 4515 4516 4517 4518 4519 4520 4521 4522 4523 4524 4525 4526 4527 4528 4529 4530 4531 4532 4533 4534 4535 4536 4537 4538 4539 4540 4541 4542 4543 4544 4545 4546 4547 4548 4549 4550 4551 4552 4553 4554 4555 4556 4557 4558 4559 4560 4561 4562 4563 4564 4565 4566 
      <p>Specifies the interval at which the sweeper process evaluates current CPU usage. When a new
        statement becomes active, its priority is evaluated and its CPU share determined when the
        next interval is reached.</p>
      <table id="gp_resqueue_priority_sweeper_interval_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">500 - 15000 ms</entry>
              <entry colname="col2">1000</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_role">
    <title>gp_role</title>
    <body>
      <p>The role of this server process " set to <i>dispatch</i> for the master and <i>execute</i>
        for a segment.</p>
      <table id="gp_role_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">dispatch<p>execute</p><p>utility</p></entry>
              <entry colname="col2"/>
              <entry colname="col3">read only</entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_safefswritesize">
    <title>gp_safefswritesize</title>
    <body>
      <p>Specifies a minimum size for safe write operations to append-optimized tables in a
        non-mature file system. When a number of bytes greater than zero is specified, the
        append-optimized writer adds padding data up to that number in order to prevent data
        corruption due to file system errors. Each non-mature file system has a known safe write
        size that must be specified here when using Greenplum Database with that type of file
        system. This is commonly set to a multiple of the extent size of the file system; for
        example, Linux ext3 is 4096 bytes, so a value of 32768 is commonly used.</p>
      <table id="gp_safefswritesize_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
              <entry colname="col2">0</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_segment_connect_timeout">
    <title>gp_segment_connect_timeout</title>
    <body>
      <p>Time that the Greenplum interconnect will try to connect to a segment instance over the
        network before timing out. Controls the network connection timeout between master and
        primary segments, and primary to mirror segment replication processes.</p>
      <table id="gp_segment_connect_timeout_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Any valid time expression (number and unit)</entry>
F
Modify gp_segment_connect_timeout in document & postgresql.conf.sample to...  
Fenggang Wang 已提交
4567 
              <entry colname="col2">3min</entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
4568 4569 4570 4571 4572 4573 4574 4575 4576 4577 
              <entry colname="col3">local<p>system</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_segments_for_planner">
    <title>gp_segments_for_planner</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
4578 
      <p>Sets the number of primary segment instances for the Postgres Planner to
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
4579 
        assume in its cost and size estimates. If 0, then the value used is the actual number of
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
4580 
        primary segments. This variable affects the Postgres Planner's estimates of the number of
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
4581 4582 4583 4584 4585 4586 4587 4588 4589 4590 4591 4592 4593 4594 4595 4596 4597 4598 4599 4600 4601 4602 4603 4604 4605 4606 4607 4608 4609 4610 4611 4612 4613 4614 4615 4616 4617 4618 4619 4620 4621 4622 4623 4624 4625 4626 4627 4628 4629 4630 4631 4632 4633 4634 4635 4636 4637 4638 4639 4640 4641 4642 4643 4644 4645 4646 4647 4648 4649 4650 4651 4652 4653 4654 4655 4656 4657 4658 4659 4660 4661 4662 4663 4664 4665 4666 4667 4668 4669 4670 4671 4672 4673 4674 4675 4676 4677 4678 4679 4680 4681 4682 4683 4684 4685 4686 4687 4688 4689 4690 4691 4692 4693 4694 4695 4696 4697 4698 4699 4700 4701 4702 4703 4704 4705 4706 4707 4708 4709 4710 4711 4712 4713 4714 4715 4716 4717 4718 4719 4720 4721 4722 4723 4724 4725 4726 4727 4728 4729 4730 4731 4732 4733 4734 4735 4736 4737 4738 4739 4740 4741 4742 4743 4744 4745 4746 4747 4748 4749 4750 4751 4752 
        rows handled by each sending and receiving process in Motion operators.</p>
      <table id="gp_segments_for_planner_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">0-<i>n</i></entry>
              <entry colname="col2">0</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_server_version">
    <title>gp_server_version</title>
    <body>
      <p>Reports the version number of the server as a string. A version modifier argument might be
        appended to the numeric portion of the version string, example: <i>5.0.0 beta</i>.</p>
      <table id="gp_server_version_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">String. Examples: <i>5.0.0</i></entry>
              <entry colname="col2">n/a</entry>
              <entry colname="col3">read only</entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_server_version_num">
    <title>gp_server_version_num</title>
    <body>
      <p>Reports the version number of the server as an integer. The number is guaranteed to always
        be increasing for each version and can be used for numeric comparisons. The major version is
        represented as is, the minor and patch versions are zero-padded to always be double digit
        wide.</p>
      <table id="gp_server_version_num_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1"><i>Mmmpp</i> where <i>M</i> is the major version, <i>mm</i> is
                the minor version zero-padded and <i>pp</i> is the patch version zero-padded.
                Example: 50000 </entry>
              <entry colname="col2">n/a</entry>
              <entry colname="col3">read only</entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_session_id">
    <title>gp_session_id</title>
    <body>
      <p>A system assigned ID number for a client session. Starts counting from 1 when the master
        instance is first started.</p>
      <table id="gp_session_id_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">1-<i>n</i></entry>
              <entry colname="col2">14</entry>
              <entry colname="col3">read only</entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_set_proc_affinity">
    <title>gp_set_proc_affinity</title>
    <body>
      <p>If enabled, when a Greenplum server process (postmaster) is started it will bind to a
        CPU.</p>
      <table id="gp_set_proc_affinity_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_set_read_only">
    <title>gp_set_read_only</title>
    <body>
      <p>Set to on to disable writes to the database. Any in progress transactions must finish
        before read-only mode takes affect.</p>
      <table id="gp_set_read_only_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_statistics_pullup_from_child_partition">
    <title>gp_statistics_pullup_from_child_partition</title>
    <body>
      <p>Enables the use of statistics from child tables when planning queries on the parent table
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
4753 
        by the Postgres Planner.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
4754 4755 4756 4757 4758 4759 4760 4761 4762 4763 4764 4765 4766 4767 4768 4769 4770 4771 4772 4773 4774 4775 4776 4777 4778 4779 
      <table id="gp_statistics_pullup_from_child_partition_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_statistics_use_fkeys">
    <title>gp_statistics_use_fkeys</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
4780 
      <p>When enabled, allows the Postgres Planner to use foreign key information
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
4781 4782 4783 4784 4785 4786 4787 4788 4789 4790 4791 4792 4793 4794 4795 4796 4797 4798 4799 4800 4801 4802 4803 4804 
        stored in the system catalog to optimize joins between foreign keys and primary keys. </p>
      <table id="gp_statistics_use_fkeys_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
M
docs - updates for online expand (#6719)  
Mel Kiyama 已提交
4805 4806 4807 4808 4809 4810 
  <topic id="gp_use_legacy_hashops">
    <title>gp_use_legacy_hashops</title>
    <body>
      <p>For a table that is defined with a <codeph>DISTRIBUTED BY
          <varname>key_column</varname></codeph> clause, this parameter controls the hash algorithm
        that is used to distribute table data among segment instances. The default value is
M
docs - fixed typo and removed draft comment.  
mkiyama 已提交
4811 
          <codeph>false</codeph>, use the jump consistent hash algorithm. </p>
M
docs - updates for online expand (#6719)  
Mel Kiyama 已提交
4812 4813 4814 4815 4816 4817 4818 4819 4820 4821 4822 4823 4824 4825 4826 4827 4828 4829 4830 4831 4832 4833 4834 4835 4836 
      <p>Setting the value to <codeph>true</codeph> uses the modulo hash algorithm that is
        compatible with Greenplum Database 5.x and earlier releases.</p>
      <table id="gp_interconnect_fc_method_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">false</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
4837 4838 4839 4840 4841 4842 4843 4844 4845 4846 4847 4848 4849 4850 4851 4852 4853 4854 4855 4856 4857 4858 4859 4860 4861 4862 4863 4864 4865 4866 4867 4868 
  <topic id="gp_vmem_idle_resource_timeout">
    <title>gp_vmem_idle_resource_timeout</title>
    <body>
      <p>If a database session is idle for longer than the time specified, the session will free
        system resources (such as shared memory), but remain connected to the database. This allows
        more concurrent connections to the database at one time.</p>
      <table id="gp_vmem_idle_resource_timeout_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Any valid time expression (number and unit)</entry>
              <entry colname="col2">18s</entry>
              <entry colname="col3">master<p>system</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_vmem_protect_limit">
    <title>gp_vmem_protect_limit</title>
    <body>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
4869 4870 
      <note>The <codeph>gp_vmem_protect_limit</codeph> server configuration parameter is enforced
        only when resource queue-based resource management is active.</note>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
4871 4872 4873 4874 4875 4876 4877 4878 4879 4880 4881 4882 4883 4884 4885 4886 4887 4888 4889 4890 4891 4892 4893 4894 4895 4896 4897 4898 4899 4900 4901 4902 4903 4904 4905 4906 4907 4908 4909 4910 4911 4912 4913 4914 4915 4916 4917 4918 4919 4920 4921 4922 4923 4924 4925 4926 4927 4928 4929 4930 4931 4932 4933 4934 4935 4936 4937 4938 4939 4940 4941 4942 4943 4944 4945 4946 4947 4948 4949 4950 4951 4952 4953 4954 4955 4956 4957 4958 4959 
      <p>Sets the amount of memory (in number of MBs) that all postgres processes of an active
        segment instance can consume. If a query causes this limit to be exceeded, memory will not
        be allocated and the query will fail. Note that this is a local parameter and must be set
        for every segment in the system (primary and mirrors). When setting the parameter value,
        specify only the numeric value. For example, to specify 4096MB, use the value
          <codeph>4096</codeph>. Do not add the units <codeph>MB</codeph> to the value.</p>
      <p>To prevent over-allocation of memory, these calculations can estimate a safe
          <codeph>gp_vmem_protect_limit</codeph> value.</p>
      <p>First calculate the value <varname>gp_vmem</varname>. This is the Greenplum Database memory
        available on a
        host<codeblock><varname>gp_vmem</varname> = ((<varname>SWAP</varname> + <varname>RAM</varname>) – (7.5GB + 0.05 * <varname>RAM</varname>)) / 1.7</codeblock></p>
      <p>where <varname>SWAP</varname> is the host swap space and <varname>RAM</varname> is the RAM
        on the host in GB.</p>
      <p>Next, calculate the <varname>max_acting_primary_segments</varname>. This is the maximum
        number of primary segments that can be running on a host when mirror segments are activated
        due to a failure. With mirrors arranged in a 4-host block with 8 primary segments per host,
        for example, a single segment host failure would activate two or three mirror segments on
        each remaining host in the failed host's block. The
          <varname>max_acting_primary_segments</varname> value for this configuration is 11 (8
        primary segments plus 3 mirrors activated on failure). </p>
      <p>This is the calculation for <codeph>gp_vmem_protect_limit</codeph>. The value should be
        converted to MB.</p>
      <codeblock><codeph>gp_vmem_protect_limit</codeph> = <varname>gp_vmem</varname> / <varname>acting_primary_segments</varname></codeblock>
      <p>For scenarios where a large number of workfiles are generated, this is the calculation for
          <varname>gp_vmem</varname> that accounts for the workfiles.</p>
      <codeblock><varname>gp_vmem</varname> = ((<varname>SWAP</varname> + <varname>RAM</varname>) – (7.5GB + 0.05 * <varname>RAM</varname> - (300KB * <varname>total_#_workfiles</varname>))) / 1.7</codeblock>
      <p>For information about monitoring and managing workfile usage, see the <cite>Greenplum
          Database Administrator Guide</cite>.</p>
      <p>Based on the <varname>gp_vmem</varname> value you can calculate the value for the
          <codeph>vm.overcommit_ratio</codeph> operating system kernel parameter. This parameter is
        set when you configure each Greenplum Database host.
        <codeblock>vm.overcommit_ratio = (<varname>RAM</varname> - (0.026 * <varname>gp_vmem</varname>)) / <varname>RAM</varname></codeblock></p>
      <note>The default value for the kernel parameter <codeph>vm.overcommit_ratio</codeph> in Red
        Hat Enterprise Linux is 50. </note>
      <p>For information about the kernel parameter, see the <cite>Greenplum Database Installation
          Guide</cite>.</p>
      <table id="gp_vmem_protect_limit_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
              <entry colname="col2">8192</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_vmem_protect_segworker_cache_limit">
    <title>gp_vmem_protect_segworker_cache_limit</title>
    <body>
      <p>If a query executor process consumes more than this configured amount, then the process
        will not be cached for use in subsequent queries after the process completes. Systems with
        lots of connections or idle processes may want to reduce this number to free more memory on
        the segments. Note that this is a local parameter and must be set for every segment.</p>
      <table id="gp_vmem_protect_segworker_cache_limit_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">number of megabytes</entry>
              <entry colname="col2">500</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
H
Re-implement compression of hash join/agg spill files.  
Heikki Linnakangas 已提交
4960 4961 4962 4963 
  <topic id="gp_workfile_compression">
    <title>gp_workfile_compression</title>
    <body>
      <p>Specifies whether the temporary files created, when a hash aggregation or hash join
M
docs - update compression information (#6929)  
Mel Kiyama 已提交
4964 
        operation spills to disk, are compressed. </p>
H
Re-implement compression of hash join/agg spill files.  
Heikki Linnakangas 已提交
4965 
      <p>If your Greenplum Database installation uses serial ATA (SATA) disk drives, enabling
M
docs - update compression information (#6929)  
Mel Kiyama 已提交
4966 
        compression might help to avoid overloading the disk subsystem with IO operations.</p>
H
Re-implement compression of hash join/agg spill files.  
Heikki Linnakangas 已提交
4967 4968 4969 4970 4971 4972 4973 4974 4975 4976 4977 4978 4979 4980 4981 4982 4983 4984 4985 4986 4987 4988 4989 
      <table id="gp_workfile_compression_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
4990 4991 4992 4993 4994 4995 4996 4997 4998 4999 5000 5001 5002 5003 5004 5005 5006 5007 5008 5009 5010 5011 5012 5013 5014 5015 5016 5017 5018 5019 5020 5021 5022 5023 5024 5025 5026 5027 5028 5029 5030 5031 5032 5033 5034 5035 5036 5037 5038 5039 5040 5041 5042 5043 5044 5045 5046 5047 5048 5049 5050 5051 5052 5053 5054 5055 5056 5057 5058 5059 5060 5061 5062 5063 5064 5065 5066 5067 5068 5069 5070 5071 5072 5073 5074 5075 5076 5077 5078 5079 5080 
  <topic id="gp_workfile_limit_files_per_query">
    <title>gp_workfile_limit_files_per_query</title>
    <body>
      <p> Sets the maximum number of temporary spill files (also known as workfiles) allowed per
        query per segment. Spill files are created when executing a query that requires more memory
        than it is allocated. The current query is terminated when the limit is exceeded. </p>
      <p>Set the value to 0 (zero) to allow an unlimited number of spill files. master session
        reload</p>
      <table id="gp_workfile_limit_files_per_query_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
              <entry colname="col2">100000</entry>
              <entry colname="col3">master<p>session</p><p> reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_workfile_limit_per_query">
    <title>gp_workfile_limit_per_query</title>
    <body>
      <p>Sets the maximum disk size an individual query is allowed to use for creating temporary
        spill files at each segment. The default value is 0, which means a limit is not enforced. </p>
      <table id="gp_workfile_limit_per_query_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">kilobytes</entry>
              <entry colname="col2">0</entry>
              <entry colname="col3">master <p>session </p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gp_workfile_limit_per_segment">
    <title>gp_workfile_limit_per_segment</title>
    <body>
      <p>Sets the maximum total disk size that all running queries are allowed to use for creating
        temporary spill files at each segment. The default value is 0, which means a limit is not
        enforced. </p>
      <table id="gp_workfile_limit_per_segment_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">kilobytes</entry>
              <entry colname="col2">0</entry>
              <entry colname="col3">local <p>system </p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="gpperfmon_port">
    <title>gpperfmon_port</title>
    <body>
C
docs - GPCC no longer depends on gpperfmon_install (#7972)  
Chuck Litzell 已提交
5081 
      <p>Sets the port on which all data collection agents communicate with the
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
5082 5083 5084 5085 5086 5087 5088 5089 5090 5091 5092 5093 5094 5095 5096 5097 5098 5099 5100 5101 5102 5103 5104 5105 
        master. </p>
      <table id="gpperfmon_port_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
              <entry colname="col2">8888</entry>
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
C
Add ignore_checksum_failure GUC to reference (#2933)  
Chuck Litzell 已提交
5106 5107 5108 5109 
  <topic id="ignore_checksum_failure">
    <title>ignore_checksum_failure</title>
    <body>
      <p>Only has effect if <xref href="#data_checksums" format="dita"/> is enabled.</p>
C
revise to more accurately describe failed checksum verify behavior (#2990)  
Chuck Litzell 已提交
5110 5111 5112 5113 5114 5115 5116 5117 
      <p>Greenplum Database uses checksums to prevent loading data that has been corrupted in the
        file system into memory managed by database processes. </p>
      <p>By default, when a checksum verify error occurs when reading a heap data page, Greenplum
        Database generates an error and prevents the page from being loaded into managed memory.
        When <codeph>ignore_checksum_failure</codeph> is set to on and a checksum verify failure
        occurs, Greenplum Database generates a warning, and allows the page to be read into managed
        memory. If the page is then updated it is saved to disk and replicated to the mirror. If the
        page header is corrupt an error is reported even if this option is enabled. </p>
C
Add ignore_checksum_failure GUC to reference (#2933)  
Chuck Litzell 已提交
5118 
      <note type="warning"> Setting <codeph>ignore_checksum_failure</codeph> to on may propagate or
C
revise to more accurately describe failed checksum verify behavior (#2990)  
Chuck Litzell 已提交
5119 5120 5121 5122 5123 
        hide data corruption or lead to other serious problems. However, if a checksum failure has
        already been detected and the page header is uncorrupted, setting
          <codeph>ignore_checksum_failure</codeph> to on may allow you to bypass the error and
        recover undamaged tuples that may still be present in the table. </note>
      <p>The default setting is off, and it can only be changed by a superuser.</p>
C
Add ignore_checksum_failure GUC to reference (#2933)  
Chuck Litzell 已提交
5124 5125 5126 5127 5128 5129 5130 5131 5132 5133 5134 5135 5136 5137 5138 5139 5140 5141 5142 5143 5144 5145 5146 
      <table id="table_shd_32q_v1b">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
5147 5148 5149 5150 5151 5152 5153 5154 5155 5156 5157 5158 5159 5160 5161 5162 5163 5164 5165 5166 5167 5168 5169 5170 5171 5172 5173 5174 5175 5176 5177 5178 5179 5180 5181 5182 5183 5184 
  <topic id="integer_datetimes">
    <title>integer_datetimes</title>
    <body>
      <p>Reports whether PostgreSQL was built with support for 64-bit-integer dates and times. </p>
      <table id="integer_datetimes_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">read only</entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="IntervalStyle">
    <title>IntervalStyle</title>
    <body>
      <p>Sets the display format for interval values. The value <i>sql_standard</i> produces output
        matching SQL standard interval literals. The value <i>postgres</i> produces output matching
        PostgreSQL releases prior to 8.4 when the <xref href="#DateStyle" format="dita"/> parameter
        was set to ISO. </p>
      <p>The value <i>postgres_verbose</i> produces output matching Greenplum releases prior to 3.3
        when the <xref href="#DateStyle" format="dita"/> parameter was set to non-ISO output. </p>
      <p>The value <i>iso_8601</i> will produce output matching the time interval <i>format with
          designators</i> defined in section 4.4.3.2 of ISO 8601. See the <xref
D
Docs: Updating postgresql.org references to 9.4  
David Yozie 已提交
5185 5186 
          href="https://www.postgresql.org/docs/9.4/datatype-datetime.html" scope="external"
          format="html"><ph>PostgreSQL 9.4 documentation</ph></xref> for more information. </p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
5187 5188 5189 5190 5191 5192 5193 5194 5195 5196 5197 5198 5199 5200 5201 5202 5203 5204 5205 5206 5207 5208 5209 5210 5211 5212 5213 
      <table id="IntervalStyle_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1"
                  >postgres<p>postgres_verbose</p><p>sql_standard</p><p>iso_8601</p></entry>
              <entry colname="col2">postgres</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="join_collapse_limit">
    <title>join_collapse_limit</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
5214 
      <p>The Postgres Planner will rewrite explicit inner <codeph>JOIN</codeph>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
5215 5216 5217 5218 5219 5220 5221 5222 5223 5224 5225 5226 5227 5228 5229 5230 5231 5232 5233 5234 5235 5236 5237 5238 5239 5240 5241 5242 5243 5244 5245 5246 5247 5248 5249 5250 5251 5252 5253 5254 5255 5256 5257 5258 5259 5260 5261 5262 5263 5264 5265 5266 5267 5268 5269 5270 5271 5272 5273 5274 5275 5276 5277 5278 5279 5280 5281 5282 5283 5284 5285 5286 5287 5288 5289 5290 5291 5292 5293 5294 
        constructs into lists of <codeph>FROM</codeph> items whenever a list of no more than this
        many items in total would result. By default, this variable is set the same as
          <i>from_collapse_limit</i>, which is appropriate for most uses. Setting it to 1 prevents
        any reordering of inner JOINs. Setting this variable to a value between 1 and
          <i>from_collapse_limit</i> might be useful to trade off planning time against the quality
        of the chosen plan (higher values produce better plans). </p>
      <table id="join_collapse_limit_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">1-<i>n</i></entry>
              <entry colname="col2">20</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="keep_wal_segments">
    <title>keep_wal_segments</title>
    <body>
      <p>For Greenplum Database master mirroring, sets the maximum number of processed WAL segment
        files that are saved by the by the active Greenplum Database master if a checkpoint
        operation occurs.</p>
      <p>The segment files are used to sycnronize the active master on the standby master. </p>
      <table id="keep_wal_segments_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
              <entry colname="col2">5</entry>
              <entry colname="col3">master<p>system</p><p>reload</p><p>superuser</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="krb_caseins_users">
    <title>krb_caseins_users</title>
    <body>
      <p>Sets whether Kerberos user names should be treated case-insensitively. The default is case
        sensitive (off).</p>
      <table id="krb_caseins_users_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
C
Docs - more updates from 8.4 merge commits (#6449)  
Chuck Litzell 已提交
5295 
              <entry colname="col3">master<p>system</p><p>reload</p></entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
5296 5297 5298 5299 5300 5301 5302 5303 5304 5305 5306 5307 5308 5309 5310 5311 5312 5313 5314 5315 5316 5317 5318 5319 5320 5321 5322 5323 5324 5325 5326 5327 5328 5329 5330 5331 5332 5333 5334 5335 5336 5337 5338 5339 5340 5341 5342 5343 5344 5345 5346 5347 5348 5349 5350 5351 5352 5353 5354 5355 5356 5357 5358 5359 5360 5361 5362 5363 5364 5365 5366 5367 5368 5369 5370 5371 5372 5373 5374 5375 5376 5377 5378 5379 5380 5381 5382 5383 5384 5385 5386 5387 5388 5389 5390 5391 5392 5393 5394 5395 5396 5397 5398 5399 5400 5401 5402 5403 5404 5405 5406 5407 5408 5409 5410 5411 5412 5413 5414 5415 5416 5417 5418 5419 5420 5421 5422 5423 5424 5425 5426 5427 5428 5429 5430 5431 5432 5433 5434 5435 5436 5437 5438 5439 5440 5441 5442 5443 5444 5445 5446 5447 5448 5449 5450 5451 5452 5453 5454 5455 5456 5457 5458 5459 5460 5461 5462 5463 5464 5465 5466 5467 5468 5469 5470 5471 5472 5473 5474 5475 5476 5477 5478 5479 5480 5481 5482 5483 5484 5485 5486 5487 5488 5489 5490 5491 5492 5493 5494 5495 5496 5497 5498 5499 5500 5501 5502 5503 5504 5505 5506 5507 5508 5509 5510 5511 5512 5513 5514 5515 5516 5517 5518 5519 5520 5521 5522 5523 5524 5525 5526 5527 5528 5529 5530 5531 5532 5533 5534 5535 5536 5537 5538 5539 5540 5541 5542 5543 5544 5545 5546 5547 5548 5549 5550 5551 5552 5553 5554 5555 5556 5557 5558 5559 5560 5561 5562 
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="krb_server_keyfile">
    <title>krb_server_keyfile</title>
    <body>
      <p>Sets the location of the Kerberos server key file. </p>
      <table id="krb_server_keyfile_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">path and file name</entry>
              <entry colname="col2">unset</entry>
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="lc_collate">
    <title>lc_collate</title>
    <body>
      <p>Reports the locale in which sorting of textual data is done. The value is determined when
        the Greenplum Database array is initialized. </p>
      <table id="lc_collate_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">&lt;system dependent&gt;</entry>
              <entry colname="col2"/>
              <entry colname="col3">read only</entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="lc_ctype">
    <title>lc_ctype</title>
    <body>
      <p>Reports the locale that determines character classifications. The value is determined when
        the Greenplum Database array is initialized.</p>
      <table id="lc_ctype_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">&lt;system dependent&gt;</entry>
              <entry colname="col2"/>
              <entry colname="col3">read only</entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="lc_messages">
    <title>lc_messages</title>
    <body>
      <p>Sets the language in which messages are displayed. The locales available depends on what
        was installed with your operating system - use <i>locale -a</i> to list available locales.
        The default value is inherited from the execution environment of the server. On some
        systems, this locale category does not exist. Setting this variable will still work, but
        there will be no effect. Also, there is a chance that no translated messages for the desired
        language exist. In that case you will continue to see the English messages. </p>
      <table id="lc_messages_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">&lt;system dependent&gt;</entry>
              <entry colname="col2"/>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="lc_monetary">
    <title>lc_monetary</title>
    <body>
      <p>Sets the locale to use for formatting monetary amounts, for example with the <i>to_char</i>
        family of functions. The locales available depends on what was installed with your operating
        system - use <i>locale -a</i> to list available locales. The default value is inherited from
        the execution environment of the server. </p>
      <table id="lc_monetary_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">&lt;system dependent&gt;</entry>
              <entry colname="col2"/>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="lc_numeric">
    <title>lc_numeric</title>
    <body>
      <p>Sets the locale to use for formatting numbers, for example with the <i>to_char</i> family
        of functions. The locales available depends on what was installed with your operating system
        - use <i>locale -a</i> to list available locales. The default value is inherited from the
        execution environment of the server. </p>
      <table id="lc_numeric_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">&lt;system dependent&gt;</entry>
              <entry colname="col2"/>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="lc_time">
    <title>lc_time</title>
    <body>
      <p>This parameter currently does nothing, but may in the future.</p>
      <table id="lc_time_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">&lt;system dependent&gt;</entry>
              <entry colname="col2"/>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="listen_addresses">
    <title>listen_addresses</title>
    <body>
      <p>Specifies the TCP/IP address(es) on which the server is to listen for connections from
        client applications - a comma-separated list of host names and/or numeric IP addresses. The
        special entry * corresponds to all available IP interfaces. If the list is empty, only
        UNIX-domain sockets can connect.</p>
      <table id="listen_addresses_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">localhost,<p>host names,</p><p>IP addresses, </p><p>* (all
                  available IP interfaces)</p></entry>
              <entry colname="col2">*</entry>
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="local_preload_libraries">
    <title>local_preload_libraries</title>
    <body>
      <p>Comma separated list of shared library files to preload at the start of a client
        session.</p>
      <table id="local_preload_libraries_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1"/>
              <entry colname="col2"/>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
L
docs - add content for lock_timeout guc (#7226)  
Lisa Owen 已提交
5563 5564 5565 5566 5567 5568 5569 5570 5571 5572 5573 5574 5575 5576 5577 5578 5579 5580 5581 5582 5583 5584 5585 5586 5587 5588 5589 5590 5591 5592 5593 5594 5595 5596 5597 5598 5599 5600 5601 5602 5603 5604 5605 5606 5607 5608 5609 5610 5611 
  <topic id="lock_timeout">
    <title>lock_timeout</title>
    <body>
      <p>Abort any statement that waits longer than the specified number of
        milliseconds while attempting to acquire a lock on a table, index,
        row, or other database object. The time limit applies separately to
        each lock acquisition attempt. The limit applies both to explicit
        locking requests (such as <codeph>LOCK TABLE</codeph>, or
        <codeph>SELECT FOR UPDATE</codeph> without <codeph>NOWAIT</codeph>)
        and to implicitly-acquired locks. If <codeph>log_min_error_statement</codeph>
        is set to <codeph>ERROR</codeph> or lower, Greenplum Database logs the
        statement that timed out. A value of zero (the default) turns off this 
        lock wait monitoring.</p>
      <p>Unlike <codeph><xref href="#statement_timeout" format="dita"/></codeph>,
        this timeout can only occur while waiting for locks. Note that if
        <codeph>statement_timeout</codeph> is nonzero, it is rather pointless
        to set <codeph>lock_timeout</codeph> to the same or larger value,
        since the statement timeout would always trigger first.</p>
      <p>Greenplum Database uses the <codeph><xref href="#deadlock_timeout" format="dita"/></codeph>
        and <codeph><xref href="#gp_global_deadlock_detector_period" format="dita"/></codeph>
        to trigger local and global deadlock detection. Note that if <codeph>lock_timeout</codeph>
        is turned on and set to a value smaller than these deadlock detection
        timeouts, Greenplum Database will abort a statement before it would 
        ever trigger a deadlock check in that session.</p>
      <note>Setting <codeph>lock_timeout</codeph> in <codeph>postgresql.conf</codeph>
        is not recommended because it would affect all sessions</note>
      <table id="lock_timeout_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">0 - <codeph>INT_MAX</codeph> millisecs</entry>
              <entry colname="col2">0 millisecs</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
5612 5613 5614 5615 5616 5617 5618 5619 5620 5621 5622 5623 5624 5625 5626 5627 5628 5629 5630 5631 5632 5633 5634 5635 5636 5637 5638 5639 5640 5641 5642 5643 5644 5645 5646 5647 5648 5649 5650 5651 5652 5653 5654 5655 5656 5657 5658 5659 5660 5661 5662 5663 5664 5665 5666 5667 5668 5669 5670 5671 5672 5673 5674 5675 5676 5677 5678 5679 5680 5681 5682 5683 5684 5685 5686 5687 5688 5689 5690 5691 5692 5693 5694 5695 5696 5697 5698 5699 5700 5701 5702 5703 5704 5705 5706 5707 5708 5709 5710 5711 5712 5713 5714 5715 5716 5717 5718 5719 5720 5721 5722 5723 5724 5725 5726 5727 5728 5729 5730 5731 5732 5733 5734 5735 5736 5737 5738 5739 5740 5741 5742 5743 5744 5745 5746 5747 5748 5749 5750 5751 5752 5753 5754 5755 5756 5757 5758 5759 5760 5761 5762 5763 5764 5765 5766 5767 5768 5769 5770 5771 5772 5773 5774 5775 5776 5777 5778 5779 5780 5781 5782 5783 5784 5785 5786 5787 5788 5789 5790 5791 5792 5793 5794 5795 5796 5797 5798 5799 5800 5801 5802 5803 5804 5805 5806 5807 5808 5809 5810 5811 5812 5813 5814 5815 5816 5817 5818 5819 5820 5821 5822 5823 5824 5825 5826 5827 5828 5829 5830 5831 5832 5833 5834 5835 5836 5837 5838 5839 5840 5841 5842 5843 5844 5845 5846 5847 5848 5849 5850 5851 5852 5853 5854 5855 5856 5857 5858 5859 5860 5861 5862 5863 5864 5865 5866 5867 5868 5869 5870 5871 5872 5873 5874 5875 5876 5877 5878 5879 5880 5881 5882 5883 5884 5885 5886 5887 5888 5889 5890 5891 5892 5893 5894 5895 5896 5897 5898 5899 5900 5901 5902 5903 5904 5905 5906 5907 5908 
  <topic id="log_autostats">
    <title>log_autostats</title>
    <body>
      <p>Logs information about automatic <codeph>ANALYZE</codeph> operations related to <xref
          href="#gp_autostats_mode" format="dita"/><ph> and <xref
            href="#gp_autostats_on_change_threshold" format="dita"/></ph>.</p>
      <table id="log_autostats_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p><p>superuser</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="log_connections">
    <title>log_connections</title>
    <body>
      <p>This outputs a line to the server log detailing each successful connection. Some client
        programs, like psql, attempt to connect twice while determining if a password is required,
        so duplicate "connection received" messages do not always indicate a problem.</p>
      <table id="log_connections_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="log_disconnections">
    <title>log_disconnections</title>
    <body>
      <p>This outputs a line in the server log at termination of a client session, and includes the
        duration of the session.</p>
      <table id="log_disconnections_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="log_dispatch_stats">
    <title>log_dispatch_stats</title>
    <body>
      <p>When set to "on," this parameter adds a log message with verbose information about the
        dispatch of the statement. </p>
      <table id="log_dispatch_stats_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="log_duration">
    <title>log_duration</title>
    <body>
      <p>Causes the duration of every completed statement which satisfies <i>log_statement</i> to be
        logged.</p>
      <table id="log_duration_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p><p>superuser</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="log_error_verbosity">
    <title>log_error_verbosity</title>
    <body>
      <p>Controls the amount of detail written in the server log for each message that is
        logged.</p>
      <table id="log_error_verbosity_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">TERSE<p>DEFAULT</p><p>VERBOSE</p></entry>
              <entry colname="col2">DEFAULT</entry>
              <entry colname="col3">master<p>session</p><p>reload</p><p>superuser</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="log_executor_stats">
    <title>log_executor_stats</title>
    <body>
      <p>For each query, write performance statistics of the query executor to the server log. This
        is a crude profiling instrument. Cannot be enabled together with
        <i>log_statement_stats</i>.</p>
      <table id="log_executor_stats_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="log_hostname">
    <title>log_hostname</title>
    <body>
      <p>By default, connection log messages only show the IP address of the connecting host.
        Turning on this option causes logging of the IP address and host name of the Greenplum
        Database master. Note that depending on your host name resolution setup this might impose a
        non-negligible performance penalty. </p>
      <table id="log_hostname_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="log_min_duration_statement">
    <title>log_min_duration_statement</title>
    <body>
      <p>Logs the statement and its duration on a single log line if its duration is greater than or
        equal to the specified number of milliseconds. Setting this to 0 will print all statements
        and their durations. -1 disables the feature. For example, if you set it to 250 then all SQL
        statements that run 250ms or longer will be logged. Enabling this option can be useful in
        tracking down unoptimized queries in your applications.</p>
      <table id="log_min_duration_statement_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">number of milliseconds, 0, -1</entry>
              <entry colname="col2">-1</entry>
              <entry colname="col3">master<p>session</p><p>reload</p><p>superuser</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="log_min_error_statement">
    <title>log_min_error_statement</title>
    <body>
      <p>Controls whether or not the SQL statement that causes an error condition will also be
        recorded in the server log. All SQL statements that cause an error of the specified level or
        higher are logged. The default is PANIC (effectively turning this feature off for normal
        use). Enabling this option can be helpful in tracking down the source of any errors that
        appear in the server log.</p>
      <table id="log_min_error_statement_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">DEBUG5
                  <p>DEBUG4</p><p>DEBUG3</p><p>DEBUG2</p><p>DEBUG1</p><p>INFO</p><p>NOTICE</p><p>WARNING</p><p>ERROR</p><p>FATAL</p><p>PANIC</p></entry>
              <entry colname="col2">ERROR</entry>
              <entry colname="col3">master<p>session</p><p>reload</p><p>superuser</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="log_min_messages">
    <title>log_min_messages</title>
    <body>
      <p>Controls which message levels are written to the server log. Each level includes all the
        levels that follow it. The later the level, the fewer messages are sent to the log.</p>
M
docs: plcontainer logging and attribute updates. (#4303)  
Mel Kiyama 已提交
5909 
      <p>If the Greenplum Database PL/Container extension is installed. This parameter also controls
M
docs: minor updates. (#4344)  
Mel Kiyama 已提交
5910 
        the PL/Container log level. For information about the extension, see <xref
M
docs: plcontainer logging and attribute updates. (#4303)  
Mel Kiyama 已提交
5911 
          href="../extensions/pl_container.xml"/>.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
5912 5913 5914 5915 5916 5917 5918 5919 5920 5921 5922 5923 5924 5925 5926 5927 5928 5929 5930 5931 5932 5933 5934 5935 5936 5937 5938 5939 5940 5941 5942 5943 5944 5945 5946 5947 5948 5949 5950 5951 5952 5953 5954 5955 5956 5957 5958 5959 5960 5961 5962 5963 5964 5965 5966 5967 
      <table id="log_min_messages_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">DEBUG5
                  <p>DEBUG4</p><p>DEBUG3</p><p>DEBUG2</p><p>DEBUG1</p><p>INFO</p><p>NOTICE</p><p>WARNING</p><p>LOG</p><p>ERROR</p><p>FATAL</p><p>PANIC</p></entry>
              <entry colname="col2">WARNING</entry>
              <entry colname="col3">master<p>session</p><p>reload</p><p>superuser</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="log_parser_stats">
    <title>log_parser_stats</title>
    <body>
      <p>For each query, write performance statistics of the query parser to the server log. This is
        a crude profiling instrument. Cannot be enabled together with
        <i>log_statement_stats</i>.</p>
      <table id="log_parser_stats_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p><p>superuser</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="log_planner_stats">
    <title>log_planner_stats</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
5968 
      <p>For each query, write performance statistics of the Postgres Planner to the
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
5969 5970 5971 5972 5973 5974 5975 5976 5977 5978 5979 5980 5981 5982 5983 5984 5985 5986 5987 5988 5989 5990 5991 5992 5993 5994 5995 5996 
        server log. This is a crude profiling instrument. Cannot be enabled together with
          <i>log_statement_stats</i>.</p>
      <table id="log_planner_stats_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p><p>superuser</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="log_rotation_age">
    <title>log_rotation_age</title>
    <body>
C
Docs - change default log_rotation_size to 1GB (#7386)  
Chuck Litzell 已提交
5997 5998 5999 
      <p>Determines the amount of time Greenplum Database writes messages to the active log file.
        When this amount of time has elapsed, the file is closed and a new log file is created. Set
        to zero to disable time-based creation of new log files.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6000 6001 6002 6003 6004 6005 6006 6007 6008 6009 6010 6011 6012 6013 6014 6015 6016 6017 6018 6019 6020 6021 6022 6023 6024 6025 
      <table id="log_rotation_age_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Any valid time expression (number and unit)</entry>
              <entry colname="col2">1d</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="log_rotation_size">
    <title>log_rotation_size</title>
    <body>
C
Docs - change default log_rotation_size to 1GB (#7386)  
Chuck Litzell 已提交
6026 6027 6028 
      <p>Determines the size of an individual log file that triggers rotation. When the log file
        size is equal to or greater than this size, the file is closed and a new log file is
        created. Set to zero to disable size-based creation of new log files. </p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6029 6030 6031 6032 6033 6034 6035 6036 6037 6038 6039 6040 6041 6042 6043 6044 6045 
      <p>The maximum value is INT_MAX/1024. If an invalid value is specified, the default value is
        used. INT_MAX is the largest value that can be stored as an integer on your system. </p>
      <table id="log_rotation_size_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">number of kilobytes</entry>
C
Docs - change default log_rotation_size to 1GB (#7386)  
Chuck Litzell 已提交
6046 
              <entry colname="col2">1048576</entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6047 6048 6049 6050 6051 6052 6053 6054 6055 6056 6057 6058 6059 6060 6061 6062 6063 6064 6065 6066 6067 6068 6069 6070 6071 6072 6073 6074 6075 6076 6077 6078 6079 6080 6081 6082 6083 6084 6085 6086 6087 6088 6089 6090 6091 6092 6093 6094 6095 6096 6097 6098 6099 6100 6101 6102 6103 6104 6105 6106 6107 6108 6109 6110 6111 
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="log_statement">
    <title>log_statement</title>
    <body>
      <p>Controls which SQL statements are logged. DDL logs all data definition commands like
        CREATE, ALTER, and DROP commands. MOD logs all DDL statements, plus INSERT, UPDATE, DELETE,
        TRUNCATE, and COPY FROM. PREPARE and EXPLAIN ANALYZE statements are also logged if their
        contained command is of an appropriate type.</p>
      <table id="log_statement_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">NONE<p>DDL</p><p>MOD</p><p>ALL</p></entry>
              <entry colname="col2">ALL</entry>
              <entry colname="col3">master<p>session</p><p>reload</p><p>superuser</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="log_statement_stats">
    <title>log_statement_stats</title>
    <body>
      <p>For each query, write total performance statistics of the query parser, planner, and
        executor to the server log. This is a crude profiling instrument.</p>
      <table id="log_statement_stats_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p><p>superuser</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
J
Add doc for log_temp_files (#2969)  
Jane Beckman 已提交
6112 6113 6114 6115 
  <topic id="log_temp_files">
    <title>log_temp_files</title>
    <body>
      <p>Controls logging of temporary file names and sizes. Temporary files can be created for
M
DOCS: update gpconfig. Updated, simplified quoting syntax for GUC values (#3016)  
Mel Kiyama 已提交
6116 
        sorts, hashes, temporary query results and spill files. A log entry is made in
J
Add doc for log_temp_files (#2969)  
Jane Beckman 已提交
6117 6118 6119 6120 6121 6122 6123 6124 6125 6126 6127 6128 6129 6130 6131 6132 6133 6134 6135 6136 6137 6138 6139 6140 6141 6142 6143 6144 6145 
          <codeph>pg_log</codeph> for each temporary file when it is deleted. Depending on the
        source of the temporary files, the log entry could be created on either the master and/or
        segments. A <codeph>log_temp_files</codeph> value of zero logs all temporary file
        information, while positive values log only files whose size is greater than or equal to the
        specified number of kilobytes. The default setting is <codeph>-1</codeph>, which disables
        logging. Only superusers can change this setting.</p>
      <table id="log_temp_files_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Integer</entry>
              <entry colname="col2">-1</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6146 6147 6148 6149 6150 6151 6152 6153 6154 6155 6156 6157 6158 6159 6160 6161 6162 6163 6164 6165 6166 6167 6168 6169 6170 6171 6172 6173 6174 6175 6176 6177 6178 6179 6180 6181 6182 6183 6184 6185 6186 6187 6188 6189 6190 6191 6192 6193 6194 6195 6196 6197 6198 6199 6200 6201 6202 6203 6204 6205 6206 6207 
  <topic id="log_timezone">
    <title>log_timezone</title>
    <body>
      <p>Sets the time zone used for timestamps written in the log. Unlike <xref href="#TimeZone"
          format="dita"/>, this value is system-wide, so that all sessions will report timestamps
        consistently. The default is <codeph>unknown</codeph>, which means to use whatever the
        system environment specifies as the time zone.</p>
      <table id="log_timezone_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">string</entry>
              <entry colname="col2">unknown</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="log_truncate_on_rotation">
    <title>log_truncate_on_rotation</title>
    <body>
      <p>Truncates (overwrites), rather than appends to, any existing log file of the same name.
        Truncation will occur only when a new file is being opened due to time-based rotation. For
        example, using this setting in combination with a log_filename such as
          <codeph>gpseg#-%H.log</codeph> would result in generating twenty-four hourly log files and
        then cyclically overwriting them. When off, pre-existing files will be appended to in all
        cases.</p>
      <table id="log_truncate_on_rotation_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
adding reference topic for maintenance_work_mem, which is mentioned elsewhere...  
David Yozie 已提交
6208 6209 6210 6211 6212 6213 6214 6215 6216 6217 6218 6219 6220 6221 6222 6223 6224 6225 6226 6227 6228 6229 6230 6231 6232 6233 6234 6235 6236 6237 
  <topic id="maintenance_work_mem">
    <title>maintenance_work_mem</title>
    <body>
      <p>Specifies the maximum amount of memory to be used in maintenance operations, such as
          <codeph>VACUUM</codeph> and <codeph>CREATE INDEX</codeph>. It defaults to 16 megabytes
        (16MB). Larger settings might improve performance for vacuuming and for restoring database
        dumps.</p>
      <table id="table_wfs_tfp_qcb">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Integer</entry>
              <entry colname="col2">16</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6238 6239 6240 
  <topic id="max_appendonly_tables">
    <title>max_appendonly_tables</title>
    <body>
M
GPDB 4.3.14.0 - clarify GUC max_appendonly_tables [#145961475]  
mkiyama 已提交
6241 6242 6243 6244 6245 6246 6247 6248 6249 6250 6251 6252 6253 6254 
      <p>Sets the maximum number of concurrent transactions that can write to or update
        append-optimized tables. Transactions that exceed the maximum return an error.</p>
      <p>Operations that are counted are <codeph>INSERT</codeph>, <codeph>UPDATE</codeph>,
          <codeph>COPY</codeph>, and <codeph>VACUUM</codeph> operations. The limit is only for
        in-progress transactions. Once a transaction ends (either aborted or committed), it is no
        longer counted against this limit.</p>
      <p>For operations against a partitioned table, each subpartition (child table) that is an
        append-optimized table and is changed counts as a single table towards the maximum. For
        example, a partitioned table <codeph>p_tbl</codeph> is defined with three subpartitions that
        are append-optimized tables <codeph>p_tbl_ao1</codeph>, <codeph>p_tbl_ao2</codeph>, and
          <codeph>p_tbl_ao3</codeph>. An <codeph>INSERT</codeph> or <codeph>UPDATE</codeph> command
        against the partitioned table <codeph>p_tbl</codeph> that changes append-optimized tables
          <codeph>p_tbl_ao1</codeph> and <codeph>p_tbl_ao2</codeph> is counted as two transactions. </p>
      <p>Increasing the limit allocates more shared memory on the master host at server start.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6255 6256 6257 6258 6259 6260 6261 6262 6263 6264 6265 6266 6267 6268 6269 6270 6271 6272 6273 6274 6275 6276 6277 6278 6279 6280 6281 6282 6283 6284 6285 6286 6287 
      <table id="max_appendonly_tables_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer > 0</entry>
              <entry colname="col2">10000</entry>
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="max_connections">
    <title>max_connections</title>
    <body>
      <p>The maximum number of concurrent connections to the database server. In a Greenplum
        Database system, user client connections go through the Greenplum master instance only.
        Segment instances should allow 5-10 times the amount as the master. When you increase this
        parameter, <xref href="#max_prepared_transactions" format="dita"/> must be increased as
        well. For more information about limiting concurrent connections, see "Configuring Client
        Authentication" in the <i>Greenplum Database Administrator Guide</i>.</p>
      <p>Increasing this parameter may cause Greenplum Database to request more shared
D
docs: Fix typos and spacing in the documentation  
Daniel Gustafsson 已提交
6288 
        memory. Increasing this parameter might cause Greenplum Database to request more shared
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6289 6290 6291 6292 6293 6294 6295 6296 6297 6298 6299 6300 6301 6302 6303 6304 6305 6306 6307 6308 6309 6310 6311 6312 6313 6314 6315 6316 6317 6318 6319 6320 6321 6322 6323 6324 6325 6326 6327 6328 6329 6330 6331 6332 6333 6334 6335 6336 6337 6338 6339 6340 6341 6342 6343 6344 6345 6346 6347 6348 6349 6350 6351 6352 6353 6354 6355 6356 6357 6358 6359 6360 6361 6362 6363 6364 6365 6366 6367 6368 6369 6370 6371 6372 6373 6374 6375 6376 6377 6378 6379 6380 6381 6382 6383 6384 6385 6386 6387 6388 6389 6390 6391 6392 6393 6394 6395 6396 6397 6398 6399 6400 6401 6402 6403 6404 6405 6406 6407 6408 6409 6410 6411 6412 6413 6414 6415 6416 6417 6418 6419 6420 6421 6422 6423 6424 6425 6426 6427 6428 6429 6430 6431 6432 6433 6434 6435 6436 6437 6438 6439 6440 6441 6442 6443 6444 6445 6446 6447 6448 6449 6450 6451 6452 6453 6454 6455 6456 6457 6458 6459 6460 6461 6462 6463 6464 6465 6466 6467 6468 6469 6470 6471 6472 6473 6474 6475 6476 6477 6478 6479 6480 6481 6482 6483 6484 6485 6486 6487 6488 6489 6490 
        memory. See <xref href="#shared_buffers" format="dita"/> for information about Greenplum
        server instance shared memory buffers.</p>
      <table id="max_connections_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">10-<i>n</i></entry>
              <entry colname="col2">250 on master<p>750 on segments</p></entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="max_files_per_process">
    <title>max_files_per_process</title>
    <body>
      <p>Sets the maximum number of simultaneously open files allowed to each server subprocess. If
        the kernel is enforcing a safe per-process limit, you don't need to worry about this
        setting. Some platforms such as BSD, the kernel will allow individual processes to open many
        more files than the system can really support.</p>
      <table id="max_files_per_process_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
              <entry colname="col2">1000</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="max_function_args">
    <title>max_function_args</title>
    <body>
      <p>Reports the maximum number of function arguments. </p>
      <table id="max_function_args_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
              <entry colname="col2">100</entry>
              <entry colname="col3">read only</entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="max_identifier_length">
    <title>max_identifier_length</title>
    <body>
      <p>Reports the maximum identifier length.</p>
      <table id="max_identifier_length_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
              <entry colname="col2">63</entry>
              <entry colname="col3">read only</entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="max_index_keys">
    <title>max_index_keys</title>
    <body>
      <p>Reports the maximum number of index keys. </p>
      <table id="max_index_keys_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
              <entry colname="col2">32</entry>
              <entry colname="col3">read only</entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="max_locks_per_transaction">
    <title>max_locks_per_transaction</title>
    <body>
      <p>The shared lock table is created with room to describe locks on
          <i>max_locks_per_transaction</i> * (<i>max_connections</i> +
          <i>max_prepared_transactions</i>) objects, so no more than this many distinct objects can
        be locked at any one time. This is not a hard limit on the number of locks taken by any one
        transaction, but rather a maximum average value. You might need to raise this value if you
        have clients that touch many different tables in a single transaction.</p>
      <table id="max_locks_per_transaction_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
              <entry colname="col2">128</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="max_prepared_transactions">
    <title>max_prepared_transactions</title>
    <body>
      <p>Sets the maximum number of transactions that can be in the prepared state simultaneously.
        Greenplum uses prepared transactions internally to ensure data integrity across the
        segments. This value must be at least as large as the value of <xref href="#max_connections"
          format="dita"/> on the master. Segment instances should be set to the same value as the
        master. </p>
      <table id="max_prepared_transactions_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
              <entry colname="col2">250 on master<p>250 on segments</p></entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="max_resource_portals_per_transaction">
    <title>max_resource_portals_per_transaction</title>
    <body>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
6491 6492 
      <note>The <codeph>max_resource_portals_per_transaction</codeph> server configuration parameter
        is enforced only when resource queue-based resource management is active.</note>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6493 6494 
      <p>Sets the maximum number of simultaneously open user-declared cursors allowed per
        transaction. Note that an open cursor will hold an active query slot in a resource queue.
D
Edits to make 'resource management' using resource queues, resources … (#3353)  
David Yozie 已提交
6495 
        Used for resource management.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6496 6497 6498 6499 6500 6501 6502 6503 6504 6505 6506 6507 6508 6509 6510 6511 6512 6513 6514 6515 6516 6517 6518 6519 6520 6521 
      <table id="max_resource_portals_per_transaction_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
              <entry colname="col2">64</entry>
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="max_resource_queues">
    <title>max_resource_queues</title>
    <body>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
6522 6523 
      <note>The <codeph>max_resource_queues</codeph> server configuration parameter is enforced only
        when resource queue-based resource management is active.</note>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6524 6525 6526 
      <p>Sets the maximum number of resource queues that can be created in a Greenplum Database
        system. Note that resource queues are system-wide (as are roles) so they apply to all
        databases in the system.</p>
M
docs: add orca guc optimizer_join_arity_for_associativity_commutativity (#3520)  
Mel Kiyama 已提交
6527 
      <table id="max_resource_groups_table">
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6528 6529 6530 6531 6532 6533 6534 6535 6536 6537 6538 6539 6540 6541 6542 6543 6544 6545 6546 6547 6548 6549 6550 6551 6552 6553 6554 6555 6556 6557 6558 6559 6560 6561 6562 6563 6564 6565 6566 6567 6568 6569 6570 6571 6572 6573 6574 6575 6576 6577 6578 6579 6580 6581 6582 6583 6584 
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
              <entry colname="col2">9</entry>
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="max_stack_depth">
    <title>max_stack_depth</title>
    <body>
      <p>Specifies the maximum safe depth of the server's execution stack. The ideal setting for
        this parameter is the actual stack size limit enforced by the kernel (as set by <i>ulimit
          -s</i> or local equivalent), less a safety margin of a megabyte or so. Setting the
        parameter higher than the actual kernel limit will mean that a runaway recursive function
        can crash an individual backend process.</p>
      <table id="max_stack_depth_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">number of kilobytes</entry>
              <entry colname="col2">2MB</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="max_statement_mem">
    <title>max_statement_mem</title>
    <body>
      <p>Sets the maximum memory limit for a query. Helps avoid out-of-memory errors on a segment
M
doc: document issue when updating both max_statement_mem and statement_mem (#3269)  
Mel Kiyama 已提交
6585 6586 
        host during query processing as a result of setting <codeph><xref href="#statement_mem"
            format="dita"/>
L
docs - updates for changes to resgroup MAX_SPILL_RATIO/MEMORY_LIMIT (#7886)  
Lisa Owen 已提交
6587 6588 6589 
        </codeph>too high.</p>
      <p>Taking into account the configuration of a single segment host,
        calculate <codeph>max_statement_mem</codeph> as follows:</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6590 6591 6592 
      <p>
        <codeph>(seghost_physical_memory) / (average_number_concurrent_queries)</codeph>
      </p>
M
doc: document issue when updating both max_statement_mem and statement_mem (#3269)  
Mel Kiyama 已提交
6593 6594 6595 
      <p>When changing both <codeph>max_statement_mem</codeph> and <codeph>statement_mem</codeph>,
          <codeph>max_statement_mem</codeph> must be changed first, or listed first in the
          <systemoutput>postgresql.conf</systemoutput> file.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6596 6597 6598 6599 6600 6601 6602 6603 6604 6605 6606 6607 6608 6609 6610 6611 6612 6613 6614 6615 6616 6617 6618 
      <table id="max_statement_mem_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">number of kilobytes</entry>
              <entry colname="col2">2000MB</entry>
              <entry colname="col3">master<p>session</p><p>reload</p><p>superuser</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
L
docs - memory_spill_ratio guc and related content (#3278)  
Lisa Owen 已提交
6619 6620 6621 
  <topic id="memory_spill_ratio">
    <title>memory_spill_ratio</title>
    <body>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
6622 6623 
      <note>The <codeph>memory_spill_ratio</codeph> server configuration parameter is enforced only
        when resource group-based resource management is active.</note>
M
docs - update GUC optimizer_analyze_root_partition (#5102)  
Mel Kiyama 已提交
6624 6625 6626 6627 6628 6629 6630 6631 
      <p>Sets the memory usage threshold percentage for memory-intensive operators in a transaction.
        When a transaction reaches this threshold, it spills to disk.</p>
      <p>The default <codeph>memory_spill_ratio</codeph> percentage is the value defined for the
        resource group assigned to the currently active role. You can set
          <codeph>memory_spill_ratio</codeph> at the session level to selectively set this limit on
        a per-query basis. For example, if you have a specific query that spills to disk and
        requires more memory, you may choose to set a larger <codeph>memory_spill_ratio</codeph> to
        increase the initial memory allocation.</p>
L
docs - updates for changes to resgroup MAX_SPILL_RATIO/MEMORY_LIMIT (#7886)  
Lisa Owen 已提交
6632 6633 6634 6635 6636 
      <p>You can specify an integer percentage value from 0 to 100 inclusive. If you
        specify a value of 0, Greenplum Database uses the
            <xref href="#statement_mem" format="dita"><codeph>statement_mem</codeph></xref>
        server configuration parameter value to control the initial query operator memory
        amount.</p>
L
docs - memory_spill_ratio guc and related content (#3278)  
Lisa Owen 已提交
6637 6638 6639 6640 6641 6642 6643 6644 6645 6646 6647 6648 6649 6650 
      <table id="memory_spill_ratio_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
L
docs - 0 memory_spill_ratio, no relation to memory_shared_quota (#3410)  
Lisa Owen 已提交
6651 
              <entry colname="col1">0 - 100</entry>
L
docs - memory_spill_ratio guc and related content (#3278)  
Lisa Owen 已提交
6652 6653 6654 6655 6656 6657 6658 6659 
              <entry colname="col2">20</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6660 6661 6662 
  <topic id="optimizer">
    <title>optimizer</title>
    <body>
D
Enable gporca by default (#2423)  
David Yozie 已提交
6663 
      <p>Enables or disables GPORCA when running SQL queries. The default is <codeph>on</codeph>. If
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
6664 6665 
        you disable GPORCA, Greenplum Database uses only the Postgres Planner. </p>
      <p>GPORCA co-exists with the Postgres Planner. With GPORCA enabled, Greenplum Database
D
Enable gporca by default (#2423)  
David Yozie 已提交
6666 
        uses GPORCA to generate an execution plan for a query when possible. If GPORCA cannot be
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
6667 
        used, then the Postgres Planner is used. </p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6668 6669 
      <p>The <cmdname>optimizer</cmdname> parameter can be set for a database system, an individual
        database, or a session or query.</p>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
6670 
      <p>For information about the Postgres Planner and GPORCA, see <xref
M
docs: gporca updates (#4792)  
Mel Kiyama 已提交
6671 6672 6673 
          href="../../admin_guide/query/topics/query.xml">Querying Data</xref><ph
          otherprops="op-print"> in the <cite>Greenplum Database Administrator
        Guide</cite></ph>.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6674 6675 6676 6677 6678 6679 6680 6681 6682 6683 6684 6685 6686 6687 6688 
      <table id="optimizer_guc_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
D
Enable gporca by default (#2423)  
David Yozie 已提交
6689 
              <entry colname="col2">on</entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6690 6691 6692 6693 6694 6695 6696 6697 6698 6699 
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="optimizer_analyze_root_partition">
    <title>optimizer_analyze_root_partition</title>
    <body>
M
docs - ANALYZE command - HLL statistics, incremental analyze (#5696)  
Mel Kiyama 已提交
6700 6701 6702 
      <p>For a partitioned table, controls whether the <codeph>ROOTPARTITION</codeph> keyword is
        required to collect root partition statistics when the <cmdname>ANALYZE</cmdname> command is
        run on the table. GPORCA uses the root partition statistics when generating a query plan.
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
6703 
        The Postgres Planner does not use these statistics. </p>
M
docs - ANALYZE command - HLL statistics, incremental analyze (#5696)  
Mel Kiyama 已提交
6704 6705 6706 6707 6708 6709 6710 6711 6712 6713 6714 6715 
      <p>The default setting for the parameter is <codeph>on</codeph>, the <codeph>ANALYZE</codeph>
        command can collect root partition statistics without the <codeph>ROOTPARTITION</codeph>
        keyword. Root partition statistics are collected when you run <codeph>ANALYZE</codeph> on
        the root partition, or when you run <codeph>ANALYZE</codeph> on a child leaf partition of
        the partitioned table and the other child leaf partitions have statistics. When the value is
          <codeph>off</codeph>, you must run <codeph>ANALZYE ROOTPARTITION</codeph> to collect root
        partition statistics. </p>
      <p>When the value of the server configuration parameter <codeph><xref href="#optimizer"
            format="dita"/></codeph> is <codeph>on</codeph> (the default), the value of this
        parameter should also be <codeph>on</codeph>. For information about collecting table
        statistics on partitioned tables, see <codeph><xref href="../sql_commands/ANALYZE.xml"
          /></codeph>.</p>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
6716 
      <p>For information about the Postgres Planner and GPORCA, see <xref
M
docs: gporca updates (#4792)  
Mel Kiyama 已提交
6717 6718 6719 
          href="../../admin_guide/query/topics/query.xml">Querying Data</xref><ph
          otherprops="op-print"> in the <cite>Greenplum Database Administrator
        Guide</cite></ph>.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6720 6721 6722 6723 6724 6725 6726 6727 6728 6729 6730 6731 6732 6733 6734 
      <table id="table_gj5_k5l_vp">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
M
docs - update GUC optimizer_analyze_root_partition (#5102)  
Mel Kiyama 已提交
6735 
              <entry colname="col2">on</entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6736 6737 6738 6739 6740 6741 6742 6743 6744 6745 
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="optimizer_array_expansion_threshold">
    <title>optimizer_array_expansion_threshold</title>
    <body>
D
Enable gporca by default (#2423)  
David Yozie 已提交
6746 6747 6748 6749 
      <p>When GPORCA is enabled (the default) and is processing a query that contains a predicate
        with a constant array, the <codeph>optimizer_array_expansion_threshold</codeph> parameter
        limits the optimization process based on the number of constants in the array. If the array
        in the query predicate contains more than the number elements specified by parameter, GPORCA
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6750 6751 
        disables the transformation of the predicate into its disjunctive normal form during query
        optimization. </p>
M
docs - update optimizer_array_expansion_threshold default to 100  
mkiyama 已提交
6752 
      <p>The default value is 100. </p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6753 
      <p>For example, when GPORCA is executing a query that contains an <codeph>IN</codeph> clause
M
docs - update optimizer_array_expansion_threshold default to 100  
mkiyama 已提交
6754 
        with more than 100 elements, GPORCA does not transform the predicate into its disjunctive
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6755 6756 6757 6758 6759 6760 6761 6762 6763 6764 6765 6766 6767 6768 6769 6770 6771 6772 6773 6774 6775 6776 6777 6778 6779 6780 6781 6782 6783 6784 6785 6786 6787 6788 6789 6790 6791 6792 6793 6794 6795 6796 6797 6798 6799 6800 6801 6802 6803 6804 6805 6806 6807 6808 6809 6810 6811 6812 6813 6814 6815 6816 6817 
        normal form during query optimization to reduce optimization time consume less memory. The
        difference in query processing can be seen in the filter condition for the
          <codeph>IN</codeph> clause of the query <codeph>EXPLAIN</codeph> plan.</p>
      <p>Changing the value of this parameter changes the trade-off between a shorter optimization
        time and lower memory consumption, and the potential benefits from constraint derivation
        during query optimization, for example conflict detection and partition elimination.</p>
      <p>The parameter can be set for a database system, an individual database, or a session or
        query.</p>
      <table id="table_b4p_3rh_hw">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Integer > 0</entry>
              <entry colname="col2">25</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="optimizer_control">
    <title>optimizer_control</title>
    <body>
      <p>Controls whether the server configuration parameter <cmdname>optimizer</cmdname> can be
        changed with <cmdname>SET</cmdname>, the <cmdname>RESET</cmdname> command, or the Greenplum
        Database utility <cmdname>gpconfig</cmdname>. If the <cmdname>optimizer_control</cmdname>
        parameter value is <codeph>on</codeph>, users can set the <cmdname>optimizer</cmdname>
        parameter. If the <cmdname>optimizer_control</cmdname> parameter value is
          <codeph>off</codeph>, the <cmdname>optimizer</cmdname> parameter cannot be changed.</p>
      <table id="application_name_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>system</p><p>restart</p><p>superuser</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
M
GPDB DOCS - new GUCs from 4.3.x and mdcache (#2518)  
mkiyama 已提交
6818 6819 6820 6821 6822 6823 6824 6825 6826 6827 6828 6829 6830 6831 6832 6833 6834 6835 6836 6837 6838 6839 6840 6841 6842 6843 6844 6845 6846 6847 6848 
  <topic id="optimizer_cte_inlining_bound">
    <title>optimizer_cte_inlining_bound</title>
    <body>
      <p>When GPORCA is enabled (the default), this parameter controls the amount of inlining
        performed for common table expression (CTE) queries (queries that contain a
          <codeph>WHERE</codeph> clause). The default value, 0, disables inlining.</p>
      <p>The parameter can be set for a database system, an individual database, or a session or
        query.</p>
      <table id="table_dq1_xlj_tz">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Decimal >= 0</entry>
              <entry colname="col2">0</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
M
docs: gporca updates (#4792)  
Mel Kiyama 已提交
6849 6850 6851 6852 6853 6854 6855 6856 6857 6858 6859 6860 6861 6862 6863 6864 6865 6866 6867 6868 6869 6870 6871 6872 6873 6874 6875 6876 6877 6878 6879 6880 6881 6882 6883 6884 6885 6886 
  <topic id="optimizer_enable_associativity">
    <title>optimizer_enable_associativity</title>
    <body>
      <p dir="ltr">When GPORCA is enabled (the default), this parameter controls whether the join
        associativity transform is enabled during query optimization. The transform analyzes join
        orders. For the default value <codeph>off</codeph>, only the GPORCA dynamic programming
        algorithm for analyzing join orders is enabled. The join associativity transform largely
        duplicates the functionality of the newer dynamic programming algorithm. </p>
      <p dir="ltr">If the value is <codeph>on</codeph>, GPORCA can use the associativity transform
        during query optimization.</p>
      <p>The parameter can be set for a database system, an individual database, or a session or
        query.</p>
      <p>For information about GPORCA, see <xref
          href="../../admin_guide/query/topics/query-piv-optimizer.xml">About GPORCA</xref><ph
          otherprops="op-print"> in the <cite>Greenplum Database Administrator Guide</cite></ph>. </p>
      <table id="table_zqr_knr_hdb">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
M
docs - add GUC optimizer_enable_dml (#8725)  
Mel Kiyama 已提交
6887 6888 6889 6890 6891 6892 6893 6894 6895 6896 6897 6898 6899 6900 6901 6902 6903 6904 6905 6906 6907 6908 6909 6910 6911 6912 6913 6914 6915 6916 6917 6918 6919 6920 6921 6922 6923 
  <topic id="optimizer_enable_dml">
    <title>optimizer_enable_dml</title>
    <body>
      <p>When GPORCA is enabled (the default) and this parameter is <codeph>true</codeph> (the
        default), GPORCA attempts to execute DML commands such as <codeph>INSERT</codeph>,
          <codeph>UPDATE</codeph>, and <codeph>DELETE</codeph>. If GPORCA cannot execute the
        command, Greenplum Database falls back to the Postgres Planner.</p>
      <p>When set to <codeph>false</codeph>, Greenplum Database always falls back to the Postgres
        Planner when performing DML commands.</p>
      <p>The parameter can be set for a database system, an individual database, or a session or
        query.</p>
      <p>For information about GPORCA, see <xref
          href="../../admin_guide/query/topics/query-piv-optimizer.xml">About GPORCA</xref><ph
          otherprops="op-print"> in the <cite>Greenplum Database Administrator Guide</cite></ph>. </p>
      <table id="table_igw_npf_fjb">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">true</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6924 6925 6926 
  <topic id="optimizer_enable_master_only_queries">
    <title>optimizer_enable_master_only_queries</title>
    <body>
D
Enable gporca by default (#2423)  
David Yozie 已提交
6927 6928 
      <p dir="ltr">When GPORCA is enabled (the default), this parameter allows GPORCA to execute
        catalog queries that run only on the Greenplum Database master. For the default value
M
docs - add GUC optimizer_enable_dml (#8725)  
Mel Kiyama 已提交
6929 6930 
          <codeph>off</codeph>, only the Postgres Planner can execute catalog queries that run only
        on the Greenplum Database master.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6931 6932 6933 6934 
      <p>The parameter can be set for a database system, an individual database, or a session or
        query.</p>
      <note>Enabling this parameter decreases performance of short running catalog queries. To avoid
        this issue, set this parameter only for a session or a query. </note>
M
docs: gporca updates (#4792)  
Mel Kiyama 已提交
6935 6936 6937 
      <p>For information about GPORCA, see <xref
          href="../../admin_guide/query/topics/query-piv-optimizer.xml">About GPORCA</xref><ph
          otherprops="op-print"> in the <cite>Greenplum Database Administrator Guide</cite></ph>. </p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
6938 6939 6940 6941 6942 6943 6944 6945 6946 6947 6948 6949 6950 6951 6952 6953 6954 6955 6956 6957 6958 6959 6960 
      <table id="table_ykk_rg5_gv">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
M
docs - new GUC optimizer_enable_agg_skew_avoidance (#6547)  
Mel Kiyama 已提交
6961 6962 6963 6964 6965 6966 6967 6968 6969 6970 6971 6972 6973 6974 6975 6976 6977 6978 6979 6980 6981 6982 6983 6984 6985 6986 6987 6988 6989 6990 6991 6992 6993 6994 6995 6996 6997 6998 
  <topic id="optimizer_force_agg_skew_avoidance">
    <title>optimizer_force_agg_skew_avoidance</title>
    <body>
      <p dir="ltr">When GPORCA is enabled (the default), this parameter affects the query plan
        alternatives that GPORCA considers when 3 stage aggregate plans are generated. When the
        value is <codeph>true</codeph>, the default, GPORCA considers only 3 stage aggregate plans
        where the intermediate aggregation uses the <codeph>GROUP BY</codeph> and
          <codeph>DISTINCT</codeph> columns for distribution to reduce the effects of processing
        skew. </p>
      <p>If the value is <codeph>false</codeph>, GPORCA can also consider a plan that uses
          <codeph>GROUP BY</codeph> columns for distribution. These plans might perform poorly when
        processing skew is present.</p>
      <p>For information about GPORCA, see <xref
          href="../../admin_guide/query/topics/query-piv-optimizer.xml">About GPORCA</xref><ph
          otherprops="op-print"> in the <cite>Greenplum Database Administrator Guide</cite></ph>. </p>
      <table id="table_ebp_rcr_cgb">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">true</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
M
GPDB DOCS - new GUCs from 4.3.x and mdcache (#2518)  
mkiyama 已提交
6999 7000 7001 
  <topic id="optimizer_force_multistage_agg">
    <title>optimizer_force_multistage_agg</title>
    <body>
C
docs - changes default value of optimier_force_mutlistate_agg GUC to off (#8513)  
Chuck Litzell 已提交
7002 7003 7004 7005 
      <p>For the default settings, GPORCA is enabled and this parameter is <codeph>false</codeph>,
        GPORCA makes a cost-based choice between a one- or two-stage aggregate plan for a scalar
        distinct qualified aggregate. When <codeph>true</codeph>, GPORCA chooses a multi-stage
        aggregate plan when such a plan alternative is generated.</p>
M
GPDB DOCS - new GUCs from 4.3.x and mdcache (#2518)  
mkiyama 已提交
7006 7007 7008 7009 7010 7011 7012 7013 7014 7015 7016 7017 7018 7019 7020 7021 7022 7023 7024 7025 7026 7027 7028 7029 7030 7031 7032 7033 7034 7035 7036 7037 7038 7039 7040 7041 7042 7043 7044 7045 7046 7047 7048 7049 7050 7051 7052 7053 7054 7055 7056 7057 7058 7059 7060 7061 7062 
      <p>The parameter can be set for a database system, an individual database, or a session or
        query. </p>
      <table id="table_kmz_vnr_tz">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">true</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="optimizer_force_three_stage_scalar_dqa">
    <title>optimizer_force_three_stage_scalar_dqa</title>
    <body>
      <p>For the default settings, GPORCA is enabled and this parameter is <codeph>true</codeph>,
        GPORCA chooses a plan with multistage aggregates when such a plan alternative is generated.
        When the value is <codeph>false</codeph>, GPORCA makes a cost based choice rather than a
        heuristic choice.</p>
      <p>The parameter can be set for a database system, an individual database, or a session, or
        query.</p>
      <table id="table_dqy_vnr_tz">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">true</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
M
docs: add orca guc optimizer_join_arity_for_associativity_commutativity (#3520)  
Mel Kiyama 已提交
7063 7064 7065 7066 7067 7068 
  <topic id="optimizer_join_arity_for_associativity_commutativity">
    <title>optimizer_join_arity_for_associativity_commutativity</title>
    <body>
      <p>The value is an optimization hint to limit the number of join associativity and join
        commutativity transformations explored during query optimization. The limit controls the
        alternative plans that GPORCA considers during query optimization. For example, the default
M
docs: change GUC default: optimizer_join_arity_for_associativity_comm… (#4242)  
Mel Kiyama 已提交
7069 7070 
        value of 18 is an optimization hint for GPORCA to stop exploring join associativity and join
        commutativity transformations when an n-ary join operator has more than 18 children during
M
docs: add orca guc optimizer_join_arity_for_associativity_commutativity (#3520)  
Mel Kiyama 已提交
7071 7072 7073 7074 7075 
        optimization.</p>
      <p>For a query with a large number of joins, specifying a lower value improves query
        performance by limiting the number of alternate query plans that GPORCA evaluates. However,
        setting the value too low might cause GPORCA to generate a query plan that performs
        sub-optimally.</p>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
7076 
      <p>This parameter has no effect when the <codeph>optimizer_join_order</codeph> parameter is
C
docs: optimizer_join_order guc (#4014)  
Chuck Litzell 已提交
7077 
        set to <codeph>query</codeph> or <codeph>greedy</codeph>.</p>
M
docs: add orca guc optimizer_join_arity_for_associativity_commutativity (#3520)  
Mel Kiyama 已提交
7078 7079 7080 7081 7082 7083 7084 7085 7086 7087 7088 7089 7090 7091 7092 7093 
      <p>This parameter can be set for a database system or a session.</p>
      <table id="table_lfq_3zg_nbb">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer > 0</entry>
M
docs: change GUC default: optimizer_join_arity_for_associativity_comm… (#4242)  
Mel Kiyama 已提交
7094 
              <entry colname="col2">18</entry>
M
docs: add orca guc optimizer_join_arity_for_associativity_commutativity (#3520)  
Mel Kiyama 已提交
7095 7096 7097 7098 7099 7100 7101 
              <entry colname="col3">local<p>system</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
C
docs: optimizer_join_order guc (#4014)  
Chuck Litzell 已提交
7102 7103 7104 
  <topic id="optimizer_join_order">
    <title>optimizer_join_order</title>
    <body>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
7105 7106 
      <p>When GPORCA is enabled, this parameter sets the optimization level for join ordering during
        query optimization by specifying which types of join ordering alternatives to evaluate.</p>
C
docs: optimizer_join_order guc (#4014)  
Chuck Litzell 已提交
7107 7108 
      <ul id="ul_dpf_cyr_1cb">
        <li><codeph>query</codeph> - Uses the join order specified in the query.</li>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
7109 
        <li><codeph>greedy</codeph> - Evaluates the join order specified in the query and
C
docs: optimizer_join_order guc (#4014)  
Chuck Litzell 已提交
7110 
          alternatives based on minimum cardinalities of the relations in the joins.</li>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
7111 7112 
        <li><codeph>exhaustive</codeph> - Applies transformation rules to find and evaluate all join
          ordering alternatives.</li>
C
docs: optimizer_join_order guc (#4014)  
Chuck Litzell 已提交
7113 
      </ul>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
7114 7115 7116 7117 7118 7119 7120 7121 
      <p>The default value is <codeph>exhaustive</codeph>. Setting this parameter to
          <codeph>query</codeph> or <codeph>greedy</codeph> can generate a suboptimal query plan.
        However, if the administrator is confident that a satisfactory plan is generated with the
          <codeph>query</codeph> or <codeph>greedy</codeph> setting, query optimization time can be
        improved by setting the parameter to the lower optimization level.</p>
      <p>Setting this parameter to <codeph>query</codeph> or <codeph>greedy</codeph> overrides the
          <codeph>optimizer_join_order_threshold </codeph> and
          <codeph>optimizer_join_arity_for_associativity_commutativity</codeph> parameters. </p>
C
docs: optimizer_join_order guc (#4014)  
Chuck Litzell 已提交
7122 7123 7124 7125 7126 7127 7128 7129 7130 7131 7132 7133 7134 7135 7136 7137 7138 7139 7140 7141 7142 7143 7144 7145 
      <p>This parameter can be set for an individual database, a session, or a query. </p>
      <table id="table_ucb_str_1cb">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">query<p>greedy</p><p>exhaustive</p></entry>
              <entry colname="col2">exhaustive</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
7146 7147 7148 
  <topic id="optimizer_join_order_threshold">
    <title>optimizer_join_order_threshold</title>
    <body>
M
GPDB DOCS - new GUCs from 4.3.x and mdcache (#2518)  
mkiyama 已提交
7149 7150 7151 
      <p>When GPORCA is enabled (the default), this parameter sets the maximum number of join
        children for which GPORCA will use the dynamic programming-based join ordering algorithm.
        You can set this value for a single query or for an entire session.</p>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
7152 
      <p>This parameter has no effect when the <codeph>optimizer_join_query</codeph> parameter is
C
docs: optimizer_join_order guc (#4014)  
Chuck Litzell 已提交
7153 
        set to <codeph>query</codeph> or <codeph>greedy</codeph>.</p>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
7154 
      <table id="table_z1c_bqp_jx">
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
7155 7156 7157 7158 7159 7160 7161 7162 7163 7164 7165 7166 7167 
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
7168 
              <entry colname="col1">0 - 12</entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
7169 7170 7171 7172 7173 7174 7175 7176 
              <entry colname="col2">10</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
M
GPDB DOCS - new GUCs from 4.3.x and mdcache (#2518)  
mkiyama 已提交
7177 7178 7179 7180 7181 7182 7183 7184 7185 7186 7187 7188 7189 7190 7191 7192 7193 7194 7195 7196 7197 7198 7199 7200 7201 7202 7203 7204 7205 7206 7207 7208 7209 7210 7211 7212 7213 7214 7215 7216 7217 7218 7219 7220 7221 7222 7223 7224 7225 7226 7227 7228 7229 7230 7231 7232 7233 7234 7235 7236 7237 7238 7239 7240 7241 7242 7243 7244 7245 7246 7247 7248 7249 7250 7251 7252 
  <topic id="optimizer_mdcache_size">
    <title>optimizer_mdcache_size</title>
    <body>
      <p dir="ltr">Sets the maximum amount of memory on the Greenplum Database master that GPORCA
        uses to cache query metadata (optimization data) during query optimization. The memory limit
        session based. GPORCA caches query metadata during query optimization with the default
        settings: GPORCA is enabled and <codeph><xref href="#optimizer_metadata_caching"
            format="dita">optimizer_metadata_caching</xref></codeph> is <codeph>on</codeph>. </p>
      <p dir="ltr">The default value is 16384 (16MB). This is an optimal value that has been
        determined through performance analysis.</p>
      <p dir="ltr">You can specify a value in KB, MB, or GB. The default unit is KB. For example, a
        value of 16384 is 16384KB. A value of 1GB is the same as 1024MB or 1048576KB. If the value
        is 0, the size of the cache is not limited. </p>
      <p>This parameter can be set for a database system, an individual database, or a session or
        query.</p>
      <table id="optimizer_mdcache_size_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Integer >= 0</entry>
              <entry colname="col2">16384</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="optimizer_metadata_caching">
    <title>optimizer_metadata_caching</title>
    <body>
      <p dir="ltr" id="docs-internal-guid-698e4ca6-574c-b75b-5cbe-8c7bfd011557">When GPORCA is
        enabled (the default), this parameter specifies whether GPORCA caches query metadata
        (optimization data) in memory on the Greenplum Database master during query optimization.
        The default for this parameter is <codeph>on</codeph>, enable caching. The cache is session
        based. When a session ends, the cache is released. If the amount of query metadata exceeds
        the cache size, then old, unused metadata is evicted from the cache. </p>
      <p dir="ltr">If the value is <codeph>off</codeph>, GPORCA does not cache metadata during query
        optimization.</p>
      <p>This parameter can be set for a database system, an individual database, or a session or
        query.</p>
      <p>The server configuration parameter <codeph><xref href="#optimizer_mdcache_size"
            format="dita"/></codeph> controls the size of the query metadata cache.</p>
      <table id="optimizer_metadata_caching_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
7253 7254 7255 7256 
  <topic id="optimizer_minidump">
    <title>optimizer_minidump</title>
    <body>
      <p>GPORCA generates minidump files to describe the optimization context for a given query. The
D
Removing pivotal references (#2619)  
David Yozie 已提交
7257 7258 7259 
        information in the file is not in a format that can be easily used for debugging or
        troubleshooting. The minidump file is located under the master data directory and uses the
        following naming format:</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
7260 7261 7262 7263 7264 7265 7266 
      <p>
        <codeph>Minidump_<varname>date</varname>_<varname>time</varname>.mdp</codeph>
      </p>
      <p>The minidump file contains this query related information:<ul id="ul_r2x_qbg_jr">
          <li>Catalog objects including data types, tables, operators, and statistics required by
            GPORCA</li>
          <li>An internal representation (DXL) of the query</li>
D
Removing pivotal references (#2619)  
David Yozie 已提交
7267 
          <li>An internal representation (DXL) of the plan produced by GPORCA</li>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
7268 7269 7270 7271 7272 7273 
          <li>System configuration information passed to GPORCA such as server configuration
            parameters, cost and statistics configuration, and number of segments</li>
          <li>A stack trace of errors generated while optimizing the query</li>
        </ul></p>
      <p>Setting this parameter to <codeph>ALWAYS</codeph> generates a minidump for all queries. Set
        this parameter to <codeph>ONERROR</codeph> to minimize total optimization time. </p>
M
docs: gporca updates (#4792)  
Mel Kiyama 已提交
7274 7275 7276 
      <p>For information about GPORCA, see <xref
          href="../../admin_guide/query/topics/query-piv-optimizer.xml">About GPORCA</xref><ph
          otherprops="op-print"> in the <cite>Greenplum Database Administrator Guide</cite></ph>. </p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
7277 7278 7279 7280 7281 7282 7283 7284 7285 7286 7287 7288 7289 7290 7291 7292 7293 7294 7295 7296 7297 7298 7299 
      <table id="optimizer_minidump">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">ONERROR<p>ALWAYS</p></entry>
              <entry colname="col2">ONERROR</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
M
GPDB DOCS - new GUCs from 4.3.x and mdcache (#2518)  
mkiyama 已提交
7300 7301 7302 
  <topic id="optimizer_nestloop_factor">
    <title>optimizer_nestloop_factor</title>
    <body>
D
Docs: Fix description, value range, and defaults for optimizer_nestloop_factor (#5188)  
David Yozie 已提交
7303 7304 7305 7306 7307 7308 
      <p>This parameter adds a costing factor to GPORCA to prioritize hash joins instead of nested
        loop joins during query optimization. The default value of 1024 was chosen after evaluating
        numerous workloads with uniformly distributed data. 1024 should be treated as the practical
        upper bound setting for this parameter. If you find the GPORCA selects hash joins more often
        than it should, reduce the value to shift the costing factor in favor of nested loop
        joins.</p>
M
GPDB DOCS - new GUCs from 4.3.x and mdcache (#2518)  
mkiyama 已提交
7309 7310 7311 7312 7313 7314 7315 7316 7317 7318 7319 7320 7321 7322 7323 7324 
      <p>The parameter can be set for a database system, an individual database, or a session or
        query.</p>
      <table id="table_zy2_xlj_tz">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
D
Docs: Fix description, value range, and defaults for optimizer_nestloop_factor (#5188)  
David Yozie 已提交
7325 7326 
              <entry colname="col1">INT_MAX > 1</entry>
              <entry colname="col2">1024</entry>
M
GPDB DOCS - new GUCs from 4.3.x and mdcache (#2518)  
mkiyama 已提交
7327 7328 7329 7330 7331 7332 7333 
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
7334 7335 7336 
  <topic id="optimizer_parallel_union">
    <title>optimizer_parallel_union</title>
    <body>
D
Enable gporca by default (#2423)  
David Yozie 已提交
7337 7338 7339 
      <p>When GPORCA is enabled (the default), <codeph>optimizer_parallel_union</codeph> controls
        the amount of parallelization that occurs for queries that contain a <codeph>UNION</codeph>
        or <codeph>UNION ALL</codeph> clause. </p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
7340 7341 7342 7343 7344 7345 7346 7347 7348 7349 7350 7351 7352 7353 7354 7355 7356 7357 7358 7359 7360 7361 7362 7363 7364 7365 7366 7367 7368 7369 7370 7371 
      <p>When the value is <codeph>off</codeph>, the default, GPORCA generates a query plan where
        each child of an APPEND(UNION) operator is in the same slice as the APPEND operator. During
        query execution, the children are executed in a sequential manner. </p>
      <p>When the value is <codeph>on</codeph>, GPORCA generates a query plan where a redistribution
        motion node is under an APPEND(UNION) operator. During query execution, the children and the
        parent APPEND operator are on different slices, allowing the children of the APPEND(UNION)
        operator to execute in parallel on segment instances.</p>
      <p>The parameter can be set for a database system, an individual database, or a session or
        query.</p>
      <table id="table_q4c_34y_rw">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
M
docs - add GUC optimizer_penalize_skew (#8474)  
Mel Kiyama 已提交
7372 7373 7374 7375 7376 7377 7378 7379 7380 7381 7382 7383 7384 7385 7386 7387 7388 7389 7390 7391 7392 7393 7394 7395 7396 7397 7398 7399 7400 7401 7402 7403 7404 7405 7406 7407 
  <topic id=" optimizer_penalize_skew">
    <title>optimizer_penalize_skew</title>
    <body>
      <p dir="ltr">When GPORCA is enabled (the default), this parameter allows GPORCA to penalize
        the local cost of a HashJoin with a skewed Redistribute Motion as child to favor a Broadcast
        Motion during query optimization. The default value is <codeph>true</codeph>. </p>
      <p dir="ltr">GPORCA determines there is skew for a Redistribute Motion when the NDV (number of
        distinct values) is less than the number of segments. </p>
      <p>The parameter can be set for a database system, an individual database, or a session or
        query.</p>
      <p>For information about GPORCA, see <xref
          href="../../admin_guide/query/topics/query-piv-optimizer.xml">About GPORCA</xref><ph
          otherprops="op-print"> in the <cite>Greenplum Database Administrator Guide</cite></ph>. </p>
      <table id="table_s11_lln_t3b">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">true</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
M
GPDB DOCS - new GUCs from 4.3.x and mdcache (#2518)  
mkiyama 已提交
7408 7409 7410 7411 7412 7413 7414 7415 7416 7417 7418 7419 7420 7421 7422 7423 7424 7425 7426 7427 7428 7429 7430 7431 7432 7433 7434 7435 7436 7437 7438 7439 7440 7441 7442 7443 7444 7445 7446 7447 7448 7449 7450 7451 7452 7453 7454 
  <topic id="optimizer_print_missing_stats">
    <title>optimizer_print_missing_stats</title>
    <body>
      <p>When GPORCA is enabled (the default), this parameter controls the display of table column
        information about columns with missing statistics for a query. The default value is
          <codeph>true</codeph>, display the column information to the client. When the value is
          <codeph>false</codeph>, the information is not sent to the client.</p>
      <p>The information is displayed during query execution, or with the <codeph>EXPLAIN</codeph>
        or <codeph>EXPLAIN ANALYZE</codeph> commands.</p>
      <p>The parameter can be set for a database system, an individual database, or a session. </p>
      <table id="table_z35_fsj_tz">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">true</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="optimizer_print_optimization_stats">
    <title>optimizer_print_optimization_stats</title>
    <body>
      <p>When GPORCA is enabled (the default), this parameter enables logging of GPORCA query
        optimization statistics for various optimization stages for a query. The default value is
          <systemoutput>off</systemoutput>, do not log optimization statistics. To log the
        optimization statistics, this parameter must be set to <systemoutput>on</systemoutput> and
        the parameter <systemoutput>client_min_messages</systemoutput> must be set to
          <systemoutput>log</systemoutput>.<ul id="ul_ysz_tx2_5z">
          <li><codeph>set optimizer_print_optimization_stats = on;</codeph></li>
          <li><codeph>set client_min_messages = 'log';</codeph></li>
        </ul></p>
      <p>The information is logged during query execution, or with the <codeph>EXPLAIN</codeph> or
          <codeph>EXPLAIN ANALYZE</codeph> commands.</p>
D
docs: Fix typos and spacing in the documentation  
Daniel Gustafsson 已提交
7455 
      <p>This parameter can be set for a database system, an individual database, or a session or
M
GPDB DOCS - new GUCs from 4.3.x and mdcache (#2518)  
mkiyama 已提交
7456 7457 7458 7459 7460 7461 7462 7463 7464 7465 7466 7467 7468 7469 7470 7471 7472 7473 7474 7475 7476 7477 7478 7479 
        query.</p>
      <table id="table_pdm_kx2_5z">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
7480 7481 7482 
  <topic id="optimizer_sort_factor">
    <title>optimizer_sort_factor</title>
    <body>
D
Enable gporca by default (#2423)  
David Yozie 已提交
7483 7484 7485 7486 7487 7488 
      <p>When GPORCA is enabled (the default), <codeph>optimizer_sort_factor</codeph> controls the
        cost factor to apply to sorting operations during query optimization. The default value
          <codeph>1</codeph> specifies the default sort cost factor. The value is a ratio of
        increase or decrease from the default factor. For example, a value of <codeph>2.0</codeph>
        sets the cost factor at twice the default, and a value of <codeph>0.5</codeph> sets the
        factor at half the default.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
7489 7490 7491 7492 7493 7494 7495 7496 7497 7498 7499 7500 7501 7502 7503 7504 7505 7506 7507 7508 7509 7510 7511 7512 7513 
      <p>The parameter can be set for a database system, an individual database, or a session or
        query.</p>
      <table id="table_mrv_z1m_zx">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Decimal > 0</entry>
              <entry colname="col2">1</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
M
docs - add guc optimizer_use_gpdb_allocators (#8767)  
Mel Kiyama 已提交
7514 7515 7516 7517 7518 7519 7520 7521 7522 7523 7524 7525 7526 7527 7528 7529 7530 7531 7532 7533 7534 7535 7536 7537 7538 7539 7540 7541 7542 7543 7544 7545 7546 7547 7548 
  <topic id="optimizer_use_gpdb_allocators">
    <title>optimizer_use_gpdb_allocators</title>
    <body>
      <p>When GPORCA is enabled (the default) and this parameter is <codeph>true</codeph> (the
        default), GPORCA uses Greenplum Database memory management when executing queries. When set
        to <codeph>false</codeph>, GPORCA uses GPORCA-specific memory management. Greenplum Database
        memory management allows for faster optimization, reduced memory usage during optimization,
        and improves GPORCA support of vmem limits when compared to GPORCA-specific memory
        management.</p>
      <p>For information about GPORCA, see <xref
          href="../../admin_guide/query/topics/query-piv-optimizer.xml">About GPORCA</xref><ph
          otherprops="op-print"> in the <cite>Greenplum Database Administrator Guide</cite></ph>. </p>
      <table id="table_xlm_qxh_gjb">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">true</entry>
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
7549 7550 7551 7552 7553 7554 7555 7556 7557 7558 7559 7560 7561 7562 7563 7564 7565 7566 7567 7568 7569 7570 7571 7572 7573 7574 7575 7576 7577 7578 7579 7580 7581 7582 7583 7584 7585 7586 7587 7588 7589 7590 7591 7592 7593 7594 7595 7596 7597 7598 7599 7600 
  <topic id="password_encryption">
    <title>password_encryption</title>
    <body>
      <p>When a password is specified in <cmdname>CREATE USER</cmdname> or <cmdname>ALTER
          USER</cmdname> without writing either <cmdname>ENCRYPTED</cmdname> or
          <cmdname>UNENCRYPTED</cmdname>, this option determines whether the password is to be
        encrypted. </p>
      <table id="password_encryption_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="password_hash_algorithm">
    <title>password_hash_algorithm</title>
    <body>
      <p>Specifies the cryptographic hash algorithm that is used when storing an encrypted Greenplum
        Database user password. The default algorithm is MD5.</p>
      <p>For information about setting the password hash algorithm to protect user passwords, see
        "Protecting Passwords in Greenplum Database" in the <cite>Greenplum Database Administrator
          Guide</cite>.</p>
      <table id="password_encryption_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
A
Remove references to FIPS crypto (#2552)  
Andreas Scherbaum 已提交
7601 
              <entry colname="col1">MD5<p>SHA-256</p></entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
7602 7603 7604 7605 7606 7607 7608 7609 7610 7611 7612 7613 7614 7615 7616 7617 7618 7619 7620 7621 7622 7623 7624 7625 7626 7627 7628 7629 7630 7631 7632 7633 7634 7635 7636 7637 7638 7639 7640 7641 7642 7643 7644 7645 7646 7647 7648 7649 7650 7651 7652 7653 7654 7655 7656 7657 7658 7659 7660 7661 7662 7663 7664 7665 7666 7667 7668 7669 7670 7671 7672 7673 7674 7675 7676 7677 7678 7679 7680 7681 7682 7683 7684 7685 7686 
              <entry colname="col2">MD5</entry>
              <entry colname="col3">master<p>session</p><p>reload</p><p>superuser</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="pljava_classpath">
    <title>pljava_classpath</title>
    <body>
      <p>A colon (<codeph>:</codeph>) separated list of jar files or directories containing jar
        files needed for PL/Java functions. The full path to the jar file or directory must be
        specified, except the path can be omitted for jar files in the
          <codeph>$GPHOME/lib/postgresql/java</codeph> directory. The jar files must be installed in
        the same locations on all Greenplum hosts and readable by the <codeph>gpadmin</codeph>
        user.</p>
      <p>The <codeph>pljava_classpath</codeph> parameter is used to assemble the PL/Java classpath
        at the beginning of each user session. Jar files added after a session has started are not
        available to that session.</p>
      <p>If the full path to a jar file is specified in <codeph>pljava_classpath</codeph> it is
        added to the PL/Java classpath. When a directory is specified, any jar files the directory
        contains are added to the PL/Java classpath. The search does not descend into subdirectories
        of the specified directories. If the name of a jar file is included in
          <codeph>pljava_classpath</codeph> with no path, the jar file must be in the
          <codeph>$GPHOME/lib/postgresql/java</codeph> directory.</p>
      <note>Performance can be affected if there are many directories to search or a large number of
        jar files.</note>
      <p>If <codeph><xref href="#pljava_classpath_insecure" format="dita"
            >pljava_classpath_insecure</xref></codeph> is <codeph>false</codeph>, setting the
          <codeph>pljava_classpath</codeph> parameter requires superuser privilege. Setting the
        classpath in SQL code will fail when the code is executed by a user without superuser
        privilege. The <codeph>pljava_classpath</codeph> parameter must have been set previously by
        a superuser or in the <codeph>postgresql.conf</codeph> file. Changing the classpath in the
          <codeph>postgresql.conf</codeph> file requires a reload (<codeph>gpstop -u</codeph>). </p>
      <table id="pljava_classpath_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">string</entry>
              <entry colname="col2"/>
              <entry colname="col3">master<p>session</p><p>reload</p><p>superuser</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="pljava_classpath_insecure">
    <title>pljava_classpath_insecure</title>
    <body>
      <p>Controls whether the server configuration parameter <codeph><xref href="#pljava_classpath"
            format="dita">pljava_classpath</xref></codeph> can be set by a user without Greenplum
        Database superuser privileges. When <codeph>true</codeph>, <codeph>pljava_classpath</codeph>
        can be set by a regular user. Otherwise, <codeph><xref href="#pljava_classpath"
            format="dita">pljava_classpath</xref></codeph> can be set only by a database superuser.
        The default is <codeph>false</codeph>.</p>
      <note type="warning">Enabling this parameter exposes a security risk by giving
        non-administrator database users the ability to run unauthorized Java methods. </note>
      <table id="table_pmx_yj4_xx">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">false</entry>
M
doc fix- pljava_classpath_insecure GUC - requires restart not reload  
mkiyama 已提交
7687 
              <entry colname="col3">master<p>session</p><p>restart</p><p>superuser</p></entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
7688 7689 7690 7691 7692 7693 7694 7695 7696 7697 7698 7699 7700 7701 7702 7703 7704 7705 7706 7707 7708 7709 7710 7711 7712 7713 7714 7715 7716 7717 7718 7719 7720 7721 7722 7723 7724 7725 7726 7727 7728 7729 7730 7731 7732 7733 7734 7735 7736 7737 7738 7739 7740 7741 7742 7743 7744 7745 7746 7747 7748 7749 7750 7751 7752 7753 7754 7755 7756 7757 7758 7759 7760 7761 7762 7763 7764 7765 7766 7767 7768 
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="pljava_statement_cache_size">
    <title>pljava_statement_cache_size</title>
    <body>
      <p>Sets the size in KB of the JRE MRU (Most Recently Used) cache for prepared statements. </p>
      <table id="pljava_statement_cache_size_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">number of kilobytes</entry>
              <entry colname="col2">10</entry>
              <entry colname="col3">master<p>system</p><p>restart</p><p>superuser</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="pljava_release_lingering_savepoints">
    <title>pljava_release_lingering_savepoints</title>
    <body>
      <p>If true, lingering savepoints used in PL/Java functions will be released on function exit.
        If false, savepoints will be rolled back.</p>
      <table id="pljava_release_lingering_savepoints_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">true</entry>
              <entry colname="col3">master<p>system</p><p>restart</p><p>superuser</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="pljava_vmoptions">
    <title>pljava_vmoptions</title>
    <body>
      <p>Defines the startup options for the Java VM. The default value is an empty string ("").</p>
      <table id="pljava_vmoptions_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">string</entry>
              <entry colname="col2"/>
M
docs: minor updates. (#4344)  
Mel Kiyama 已提交
7769 
              <entry colname="col3">master<p>system</p><p>reload</p><p>superuser</p></entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
7770 7771 7772 7773 7774 7775 7776 7777 7778 7779 7780 7781 7782 7783 7784 7785 7786 7787 7788 7789 7790 7791 7792 7793 7794 7795 7796 7797 7798 7799 7800 7801 7802 7803 7804 7805 7806 7807 7808 
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="port">
    <title>port</title>
    <body>
      <p>The database listener port for a Greenplum instance. The master and each segment has its
        own port. Port numbers for the Greenplum system must also be changed in the
          <codeph>gp_segment_configuration</codeph> catalog. You must shut down your Greenplum
        Database system before changing port numbers.</p>
      <table id="port_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">any valid port number</entry>
              <entry colname="col2">5432</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="random_page_cost">
    <title>random_page_cost</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
7809 7810 
      <p>Sets the estimate of the cost of a nonsequentially fetched disk page for the Postgres
        Planner. This is measured as a multiple of the cost of a sequential page fetch.
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
7811 7812 7813 7814 7815 7816 7817 7818 7819 7820 7821 7822 7823 7824 7825 7826 7827 7828 7829 7830 7831 7832 7833 7834 7835 7836 7837 7838 7839 7840 7841 7842 7843 7844 7845 7846 7847 7848 7849 7850 7851 7852 7853 7854 7855 7856 7857 7858 7859 7860 7861 7862 7863 7864 7865 7866 7867 7868 7869 7870 7871 7872 7873 7874 7875 7876 7877 7878 7879 7880 7881 7882 7883 7884 7885 7886 7887 7888 7889 7890 7891 7892 7893 7894 7895 7896 7897 7898 7899 7900 7901 7902 7903 7904 7905 7906 7907 7908 7909 7910 7911 7912 7913 7914 7915 7916 7917 7918 7919 7920 7921 7922 7923 7924 7925 7926 7927 7928 7929 7930 7931 7932 7933 7934 7935 7936 7937 7938 7939 7940 7941 7942 7943 7944 7945 7946 7947 7948 7949 7950 7951 7952 7953 7954 7955 7956 7957 7958 7959 7960 7961 7962 7963 7964 7965 
        A higher value makes it more likely a sequential scan will be used, a lower value makes it
        more likely an index scan will be used.</p>
      <table id="random_page_cost_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">floating point</entry>
              <entry colname="col2">100</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="readable_external_table_timeout">
    <title>readable_external_table_timeout</title>
    <body>
      <p>When an SQL query reads from an external table, the parameter value specifies the amount of
        time in seconds that Greenplum Database waits before cancelling the query when data stops
        being returned from the external table. </p>
      <p>The default value of 0, specifies no time out. Greenplum Database does not cancel the
        query. </p>
      <p>If queries that use gpfdist run a long time and then return the error "intermittent network
        connectivity issues", you can specify a value for readable_external_table_timeout. If no
        data is returned by gpfdist for the specified length of time, Greenplum Database cancels the
        query.</p>
      <table id="readable_external_table_timeout_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer &gt;= 0</entry>
              <entry colname="col2"> 0</entry>
              <entry colname="col3">master<p>system</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="repl_catchup_within_range">
    <title>repl_catchup_within_range</title>
    <body>
      <p>For Greenplum Database master mirroring, controls updates to the active master. If the
        number of WAL segment files that have not been processed by the <codeph>walsender</codeph>
        exceeds this value, Greenplum Database updates the active master. </p>
      <p>If the number of segment files does not exceed the value, Greenplum Database blocks updates
        to the to allow the <codeph>walsender</codeph> process the files. If all WAL segments have
        been processed, the active master is updated. </p>
      <table id="repl_catchup_within_range_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">0 - 64</entry>
              <entry colname="col2">1</entry>
              <entry colname="col3">master<p>system</p><p>reload</p><p>superuser</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="replication_timeout">
    <title>replication_timeout</title>
    <body>
      <p>For Greenplum Database master mirroring, sets the maximum time in milliseconds that the
          <codeph>walsender</codeph> process on the active master waits for a status message from
        the <codeph>walreceiver</codeph> process on the standby master. If a message is not
        received, the <codeph>walsender</codeph> logs an error message.</p>
      <p>The <xref href="#wal_receiver_status_interval" format="dita"/> controls the interval
        between <codeph>walreceiver</codeph> status messages. </p>
      <table id="replication_timeout_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">0 - INT_MAX</entry>
              <entry colname="col2">60000 ms (60 seconds)</entry>
              <entry colname="col3">master<p>system</p><p>reload</p><p>superuser</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="regex_flavor">
    <title>regex_flavor</title>
    <body>
      <p>The 'extended' setting may be useful for exact backwards compatibility with pre-7.4
        releases of PostgreSQL. </p>
      <table id="regex_flavor_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">advanced<p>extended</p><p>basic</p></entry>
              <entry colname="col2">advanced</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="resource_cleanup_gangs_on_wait">
    <title>resource_cleanup_gangs_on_wait</title>
    <body>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
7966 7967 
      <note>The <codeph>resource_cleanup_gangs_on_wait</codeph> server configuration parameter is
        enforced only when resource queue-based resource management is active.</note>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
7968 7969 7970 7971 7972 7973 7974 7975 7976 7977 7978 7979 7980 7981 7982 7983 7984 7985 7986 7987 7988 7989 7990 7991 7992 7993 7994 7995 
      <p>If a statement is submitted through a resource queue, clean up any idle query executor
        worker processes before taking a lock on the resource queue.</p>
      <table id="resource_cleanup_gangs_on_wait_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="resource_select_only">
    <title>resource_select_only</title>
    <body>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
7996 7997 
      <note>The <codeph>resource_select_only</codeph> server configuration parameter is enforced
        only when resource queue-based resource management is active.</note>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
7998 7999 8000 8001 8002 8003 8004 8005 8006 8007 8008 8009 8010 8011 8012 8013 8014 8015 8016 8017 8018 8019 8020 8021 8022 8023 8024 8025 8026 8027 8028 
      <p>Sets the types of queries managed by resource queues. If set to on, then
          <codeph>SELECT</codeph>, <codeph>SELECT INTO</codeph>, <codeph>CREATE TABLE AS
          SELECT</codeph>, and <codeph>DECLARE CURSOR</codeph> commands are evaluated. If set to off
          <codeph>INSERT</codeph>, <codeph>UPDATE</codeph>, and <codeph>DELETE</codeph> commands
        will be evaluated as well.</p>
      <table id="resource_select_only_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="runaway_detector_activation_percent">
    <title>runaway_detector_activation_percent</title>
    <body>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
8029 8030 
      <note>The <codeph>runaway_detector_activation_percent</codeph> server configuration parameter
        is enforced only when resource queue-based resource management is active.</note>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
8031 8032 8033 8034 8035 8036 8037 8038 8039 8040 8041 8042 8043 8044 8045 8046 8047 8048 8049 8050 8051 8052 8053 8054 8055 8056 8057 8058 8059 8060 8061 8062 8063 8064 8065 8066 8067 8068 8069 8070 8071 8072 8073 8074 8075 8076 8077 8078 8079 8080 8081 8082 8083 8084 8085 8086 8087 8088 8089 8090 
      <p>Sets the percentage of Greenplum Database vmem memory that triggers the termination of
        queries. If the percentage of vmem memory that is utilized for a Greenplum Database segment
        exceeds the specified value, Greenplum Database terminates queries based on memory usage,
        starting with the query consuming the largest amount of memory. Queries are terminated until
        the percentage of utilized vmem is below the specified percentage.</p>
      <p>Specify the maximum vmem value for active Greenplum Database segment instances with the
        server configuration parameter <xref href="#gp_vmem_protect_limit" format="dita"/>.</p>
      <p>For example, if vmem memory is set to 10GB, and the value of
          <codeph>runaway_detector_activation_percent</codeph> is 90 (90%), Greenplum Database
        starts terminating queries when the utilized vmem memory exceeds 9 GB.</p>
      <p>A value of 0 disables the automatic termination of queries based on percentage of vmem that
        is utilized.</p>
      <table id="runaway_detector_activation_percent_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">percentage (integer)</entry>
              <entry colname="col2">90</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="search_path">
    <title>search_path</title>
    <body>
      <p>Specifies the order in which schemas are searched when an object is referenced by a simple
        name with no schema component. When there are objects of identical names in different
        schemas, the one found first in the search path is used. The system catalog schema,
          <i>pg_catalog</i>, is always searched, whether it is mentioned in the path or not. When
        objects are created without specifying a particular target schema, they will be placed in
        the first schema listed in the search path. The current effective value of the search path
        can be examined via the SQL function <i>current_schemas()</i>. <i>current_schemas()</i>
        shows how the requests appearing in <i>search_path</i> were resolved.</p>
      <table id="search_path_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
C
Docs updates to gucs (#7550)  
Chuck Litzell 已提交
8091 
              <entry colname="col1">a comma-separated list of schema names</entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
8092 8093 8094 8095 8096 8097 8098 8099 8100 8101 8102 
              <entry colname="col2">$user,public</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="seq_page_cost">
    <title>seq_page_cost</title>
    <body>
D
Docs: Use 'Postgres Planner' terminology consistently (#8226)  
David Yozie 已提交
8103 
      <p>For the Postgres Planner, sets the estimate of the cost of a disk page
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
8104 8105 8106 8107 8108 8109 8110 8111 8112 8113 8114 8115 8116 8117 8118 8119 8120 8121 8122 8123 8124 8125 8126 8127 8128 8129 8130 8131 8132 8133 8134 8135 8136 8137 8138 8139 8140 8141 8142 8143 8144 8145 8146 8147 8148 8149 8150 8151 8152 8153 8154 8155 8156 8157 8158 8159 8160 8161 8162 8163 8164 8165 8166 8167 8168 8169 8170 8171 8172 8173 8174 8175 
        fetch that is part of a series of sequential fetches. </p>
      <table id="seq_page_cost_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">floating point</entry>
              <entry colname="col2">1</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="server_encoding">
    <title>server_encoding</title>
    <body>
      <p>Reports the database encoding (character set). It is determined when the Greenplum Database
        array is initialized. Ordinarily, clients need only be concerned with the value of
          <i>client_encoding</i>. </p>
      <table id="server_encoding_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">&lt;system dependent&gt;</entry>
              <entry colname="col2">UTF8</entry>
              <entry colname="col3">read only</entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="server_version">
    <title>server_version</title>
    <body>
      <p>Reports the version of PostgreSQL that this release of Greenplum Database is based on. </p>
      <table id="server_version_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">string</entry>
D
docs: Update references to upstream to 9.4  
Daniel Gustafsson 已提交
8176 
              <entry colname="col2">9.4.20</entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
8177 8178 8179 8180 8181 8182 8183 8184 8185 8186 8187 8188 8189 8190 8191 8192 8193 8194 8195 8196 8197 8198 8199 8200 8201 8202 8203 
              <entry colname="col3">read only</entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="server_version_num">
    <title>server_version_num</title>
    <body>
      <p>Reports the version of PostgreSQL that this release of Greenplum Database is based on as an
        integer.</p>
      <table id="server_version_num_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
D
docs: Update references to upstream to 9.4  
Daniel Gustafsson 已提交
8204 
              <entry colname="col2">90420</entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
8205 8206 8207 8208 8209 8210 8211 8212 8213 8214 8215 8216 8217 8218 8219 8220 8221 8222 8223 8224 8225 8226 8227 8228 8229 8230 8231 8232 8233 8234 8235 8236 8237 8238 8239 8240 8241 8242 8243 8244 8245 8246 8247 8248 8249 8250 8251 8252 8253 8254 8255 8256 8257 8258 8259 8260 8261 8262 8263 8264 8265 8266 8267 8268 8269 8270 8271 8272 8273 8274 8275 8276 8277 8278 8279 8280 8281 8282 8283 8284 8285 8286 8287 8288 8289 8290 8291 8292 8293 8294 8295 8296 8297 8298 8299 8300 8301 8302 8303 8304 8305 8306 8307 8308 8309 8310 8311 8312 8313 8314 8315 8316 8317 8318 8319 8320 8321 8322 8323 8324 8325 8326 8327 8328 8329 8330 8331 8332 8333 8334 8335 8336 8337 8338 8339 8340 8341 8342 8343 8344 8345 8346 8347 8348 8349 8350 8351 8352 8353 8354 8355 8356 
              <entry colname="col3">read only</entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="shared_buffers">
    <title>shared_buffers</title>
    <body>
      <p>Sets the amount of memory a Greenplum Database segment instance uses for shared memory
        buffers. This setting must be at least 128KB and at least 16KB times <codeph><xref
            href="#max_connections" type="section">max_connections</xref></codeph>. </p>
      <p>Each Greenplum Database segment instance calculates and attempts to allocate certain amount
        of shared memory based on the segment configuration. The value of
          <codeph>shared_buffers</codeph> is significant portion of this shared memory calculation,
        but is not all it. When setting <codeph>shared_buffers</codeph>, the values for the
        operating system parameters <codeph>SHMMAX</codeph> or <codeph>SHMALL</codeph> might also
        need to be adjusted.</p>
      <p>The operating system parameter <codeph>SHMMAX</codeph> specifies maximum size of a single
        shared memory allocation. The value of <codeph>SHMMAX</codeph> must be greater than this
        value:<codeblock> <codeph>shared_buffers</codeph> + <varname>other_seg_shmem</varname></codeblock>The
        value of <varname>other_seg_shmem</varname> is the portion the Greenplum Database shared
        memory calculation that is not accounted for by the <codeph>shared_buffers</codeph> value.
        The <varname>other_seg_shmem</varname> value will vary based on the segment configuration. </p>
      <p>With the default Greenplum Database parameter values, the value for
          <varname>other_seg_shmem</varname> is approximately 111MB for Greenplum Database segments
        and approximately 79MB for the Greenplum Database master. </p>
      <p>The operating system parameter <codeph>SHMALL</codeph> specifies the maximum amount of
        shared memory on the host. The value of <codeph>SHMALL</codeph> must be greater than this
        value:<codeblock> (<varname>num_instances_per_host</varname> * ( <codeph>shared_buffers</codeph> + <varname>other_seg_shmem</varname> )) + <varname>other_app_shared_mem</varname> </codeblock>The
        value of <varname>other_app_shared_mem</varname> is the amount of shared memory that is used
        by other applications and processes on the host. </p>
      <p>When shared memory allocation errors occur, possible ways to resolve shared memory
        allocation issues are to increase <codeph>SHMMAX</codeph> or <codeph>SHMALL</codeph>, or
        decrease <codeph>shared_buffers</codeph> or <codeph>max_connections</codeph>.</p>
      <p>See the <cite>Greenplum Database Installation Guide</cite> for information about the
        Greenplum Database values for the parameters <codeph>SHMMAX</codeph> and
          <codeph>SHMALL</codeph>. </p>
      <table id="shared_buffers_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer &gt; 16K * <i>max_connections </i></entry>
              <entry colname="col2">125MB</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="shared_preload_libraries">
    <title>shared_preload_libraries</title>
    <body>
      <p>A comma-separated list of shared libraries that are to be preloaded at server start.
        PostgreSQL procedural language libraries can be preloaded in this way, typically by using
        the syntax '<codeph>$libdir/pl<varname>XXX</varname></codeph>' where <varname>XXX</varname>
        is pgsql, perl, tcl, or python. By preloading a shared library, the library startup time is
        avoided when the library is first used. If a specified library is not found, the server will
        fail to start.</p>
      <table id="shared_preload_libraries_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1"/>
              <entry colname="col2"/>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="ssl">
    <title>ssl</title>
    <body>
      <p>Enables SSL connections. </p>
      <table id="ssl_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="ssl_ciphers">
    <title>ssl_ciphers</title>
    <body>
      <p>Specifies a list of SSL ciphers that are allowed to be used on secure connections. See the
        openssl manual page for a list of supported ciphers. </p>
      <table id="ssl_ciphers_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">string</entry>
              <entry colname="col2">ALL</entry>
              <entry colname="col3">master<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="standard_conforming_strings">
    <title>standard_conforming_strings</title>
    <body>
D
#2427: Standard conforming string default (#2429)  
David Yozie 已提交
8357 8358 8359 8360 8361 8362 
      <p>Determines whether ordinary string literals ('...') treat backslashes literally, as
        specified in the SQL standard. The default value is on. Turn this parameter off to treat
        backslashes in string literals as escape characters instead of literal backslashes.
        Applications may check this parameter to determine how string literals are processed. The
        presence of this parameter can also be taken as an indication that the escape string syntax
        (E'...') is supported.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
8363 8364 8365 8366 8367 8368 8369 8370 8371 8372 8373 8374 8375 8376 8377 
      <table id="standard_conforming_strings_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
D
#2427: Standard conforming string default (#2429)  
David Yozie 已提交
8378 
              <entry colname="col2">on</entry>
M
GPDB DOCS update set classifications for GUC standard_conforming_strings  
mkiyama 已提交
8379 
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
8380 8381 8382 8383 8384 8385 8386 8387 8388 8389 
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="statement_mem">
    <title>statement_mem</title>
    <body>
      <p>Allocates segment host memory per query. The amount of memory allocated with this parameter
M
doc: document issue when updating both max_statement_mem and statement_mem (#3269)  
Mel Kiyama 已提交
8390 
        cannot exceed <codeph><xref href="#max_statement_mem" format="dita"/></codeph> or the memory
L
docs - updates for changes to resgroup MAX_SPILL_RATIO/MEMORY_LIMIT (#7886)  
Lisa Owen 已提交
8391 8392 8393 8394 8395 8396 8397 8398 8399 8400 8401 8402 8403 8404 8405 
        limit on the resource queue or resource group through which the query was submitted.
        If additional memory is required for a query, temporary spill files on disk are used.</p>
      <p><i>If you are using resource groups to control resource allocation in your Greenplum
        Database cluster</i>:</p><ul>
        <li>Greenplum Database uses <codeph>statement_mem</codeph> to control query memory
          usage when the resource group <codeph>MEMORY_SPILL_RATIO</codeph> is set to 0.</li>
        <li>You can use the following calculation to estimate a reasonable <codeph>statement_mem</codeph>
          value:
          <codeblock>rg_perseg_mem = ((RAM * (vm.overcommit_ratio / 100) + SWAP) * gp_resource_group_memory_limit) / num_active_primary_segments
statement_mem = rg_perseg_mem / max_expected_concurrent_queries</codeblock></li>
      </ul>

      <p><i>If you are using resource queues to control resource allocation in your Greenplum
        Database cluster</i>:</p><ul>
        <li> When <codeph><xref href="#gp_resqueue_memory_policy" format="dita"/> =auto</codeph>,
M
doc: document issue when updating both max_statement_mem and statement_mem (#3269)  
Mel Kiyama 已提交
8406 
          <codeph>statement_mem</codeph> and resource queue memory limits control query memory
L
docs - updates for changes to resgroup MAX_SPILL_RATIO/MEMORY_LIMIT (#7886)  
Lisa Owen 已提交
8407 8408 8409 8410 8411 8412 8413 8414 8415 
        usage. </li>
        <li>You can use the following calculation to estimate a reasonable <codeph>statement_mem</codeph>
          value for a wide variety of situations:
          <codeblock>( <varname>gp_vmem_protect_limit</varname>GB * .9 ) / <varname>max_expected_concurrent_queries</varname></codeblock>
          <p>For example, with a <varname>gp_vmem_protect_limit</varname> set to 8192MB (8GB)
            and assuming a maximum of 40 concurrent queries with a 10% buffer, you would use
            the following calculation to determine the <codeph>statement_mem</codeph> value:</p>
          <codeblock>(8GB * .9) / 40 = .18GB = 184MB</codeblock></li>
      </ul>
M
doc: document issue when updating both max_statement_mem and statement_mem (#3269)  
Mel Kiyama 已提交
8416 8417 8418 
      <p>When changing both <codeph>max_statement_mem</codeph> and <codeph>statement_mem</codeph>,
          <codeph>max_statement_mem</codeph> must be changed first, or listed first in the
          <systemoutput>postgresql.conf</systemoutput> file.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
8419 8420 8421 8422 8423 8424 8425 8426 8427 8428 8429 8430 8431 8432 8433 8434 8435 8436 8437 8438 8439 8440 8441 8442 8443 8444 8445 8446 8447 8448 8449 8450 8451 8452 8453 8454 8455 8456 8457 8458 8459 8460 8461 8462 8463 8464 8465 8466 8467 8468 8469 8470 8471 8472 
      <table id="statement_mem_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">number of kilobytes</entry>
              <entry colname="col2">128MB</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="statement_timeout">
    <title>statement_timeout</title>
    <body>
      <p>Abort any statement that takes over the specified number of milliseconds. 0 turns off the
        limitation. </p>
      <table id="statement_timeout_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">number of milliseconds</entry>
              <entry colname="col2">0</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="stats_queue_level">
    <title>stats_queue_level</title>
    <body>
M
docs: optimizer_join_order_threshold GUC update max value (#4156)  
Mel Kiyama 已提交
8473 8474 
      <note>The <codeph>stats_queue_level</codeph> server configuration parameter is enforced only
        when resource queue-based resource management is active.</note>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
8475 8476 8477 8478 8479 8480 8481 8482 8483 8484 8485 8486 8487 8488 8489 8490 8491 8492 8493 8494 8495 8496 8497 8498 8499 8500 8501 8502 8503 8504 8505 8506 8507 8508 8509 8510 8511 8512 8513 8514 8515 8516 8517 8518 8519 8520 8521 8522 8523 8524 8525 8526 8527 8528 8529 8530 8531 
      <p>Collects resource queue statistics on database activity.</p>
      <table id="stats_queue_level_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="superuser_reserved_connections">
    <title>superuser_reserved_connections</title>
    <body>
      <p>Determines the number of connection slots that are reserved for Greenplum Database
        superusers.</p>
      <table id="superuser_reserved_connections_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer &lt; <i>max_connections</i></entry>
              <entry colname="col2">3</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="tcp_keepalives_count">
    <title>tcp_keepalives_count</title>
    <body>
      <p>How many keepalives may be lost before the connection is considered dead. A value of 0 uses
        the system default. If TCP_KEEPCNT is not supported, this parameter must be 0. </p>
M
docs - ANALYZE command - HLL statistics, incremental analyze (#5696)  
Mel Kiyama 已提交
8532 8533 
      <p>Use this parameter for all connections that are not between a primary and mirror
        segment.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
8534 8535 8536 8537 8538 8539 8540 8541 8542 8543 8544 8545 8546 8547 8548 8549 8550 8551 8552 8553 8554 8555 8556 8557 8558 8559 8560 8561 
      <table id="tcp_keepalives_count_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">number of lost keepalives</entry>
              <entry colname="col2">0</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="tcp_keepalives_idle">
    <title>tcp_keepalives_idle</title>
    <body>
      <p>Number of seconds between sending keepalives on an otherwise idle connection. A value of 0
        uses the system default. If TCP_KEEPIDLE is not supported, this parameter must be 0.</p>
M
docs - ANALYZE command - HLL statistics, incremental analyze (#5696)  
Mel Kiyama 已提交
8562 8563 
      <p>Use this parameter for all connections that are not between a primary and mirror
        segment.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
8564 8565 8566 8567 8568 8569 8570 8571 8572 8573 8574 8575 8576 8577 8578 8579 8580 8581 8582 8583 8584 8585 8586 8587 8588 8589 8590 8591 
      <table id="tcp_keepalives_idle_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">number of seconds</entry>
              <entry colname="col2">0</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="tcp_keepalives_interval">
    <title>tcp_keepalives_interval</title>
    <body>
      <p>How many seconds to wait for a response to a keepalive before retransmitting. A value of 0
        uses the system default. If TCP_KEEPINTVL is not supported, this parameter must be 0.</p>
M
docs - ANALYZE command - HLL statistics, incremental analyze (#5696)  
Mel Kiyama 已提交
8592 8593 
      <p>Use this parameter for all connections that are not between a primary and mirror
        segment.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
8594 8595 8596 8597 8598 8599 8600 8601 8602 8603 8604 8605 8606 8607 8608 8609 8610 8611 8612 8613 8614 8615 8616 8617 8618 8619 
      <table id="tcp_keepalives_interval_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">number of seconds</entry>
              <entry colname="col2">0</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="temp_buffers">
    <title>temp_buffers</title>
    <body>
C
Docs updates to gucs (#7550)  
Chuck Litzell 已提交
8620 8621 8622 8623 8624 8625 8626 8627 8628 8629 8630 8631 
      <p>Sets the maximum memory, in blocks, to allow for temporary buffers by each database
        session. These are session-local buffers used only for access to temporary tables. The
        setting can be changed within individual sessions, but only up until the first use of
        temporary tables within a session. The cost of setting a large value in sessions that do not
        actually need a lot of temporary buffers is only a buffer descriptor for each block, or
        about 64 bytes, per increment. However if a buffer is actually used, an additional 32768
        bytes will be consumed.</p>
      <p>You can set this parameter to the number of 32K blocks (for example, <codeph>1024</codeph>
        to allow 32MB for buffers), or specify the maximum amount of memory to allow (for example
          <codeph>'48MB'</codeph> for 1536 blocks). The <codeph>gpconfig</codeph> utility and
          <codeph>SHOW</codeph> command report the maximum amount of memory allowed for temporary
        buffers.</p>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
8632 8633 8634 8635 8636 8637 8638 8639 8640 8641 8642 8643 8644 8645 8646 
      <table id="temp_buffers_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
C
Docs updates to gucs (#7550)  
Chuck Litzell 已提交
8647 
              <entry colname="col2">1024 (32MB)</entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
8648 
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
D
Adding reference topic and additional docs around temp_tablespaces (#8025)  
David Yozie 已提交
8649 8650 8651 8652 8653 8654 8655 8656 8657 8658 8659 8660 8661 8662 8663 8664 8665 8666 8667 8668 8669 8670 8671 8672 8673 8674 8675 8676 8677 8678 8679 8680 8681 8682 8683 8684 8685 8686 8687 8688 8689 8690 8691 8692 8693 
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="topic_k52_fqm_f3b">
    <title>temp_tablespaces</title>
    <body>
      <p>Specifies tablespaces in which to create temporary objects (temp tables and indexes on temp
        tables) when a <codeph>CREATE</codeph> command does not explicitly specify a tablespace.
        Temporary files for purposes such as sorting large data sets are also created in these
        tablespaces.</p>
      <p>The value is a comma-separated list of names of tablespaces. When there is more than one name in the list,
        Greenplum chooses a random member of the list each time a temporary object is to be created;
        except that within a transaction, successively created temporary objects are placed in
        successive tablespaces from the list. If the selected element of the list is an empty
        string, Greenplum automatically uses the default tablespace of the current database
        instead.</p>
      <p>When <codeph>temp_tablespaces</codeph> is set interactively, specifying a nonexistent
        tablespace is an error, as is specifying a tablespace for which the user does not have
          <codeph>CREATE</codeph> privilege. However, when using a previously set value, nonexistent
        tablespaces are ignored, as are tablespaces for which the user lacks <codeph>CREATE</codeph>
        privilege. In particular, this rule applies when using a value set in
          <codeph>postgresql.conf</codeph>.</p>
      <p>The default value is an empty string, which results in all temporary objects being created
        in the default tablespace of the current database.</p>
      <p>See also <xref href="#default_tablespace" format="dita"/>.</p>
      <table id="table_l52_fqm_f3b">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">one or more tablespace names</entry>
              <entry colname="col2">unset</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
8694 8695 8696 8697 8698 8699 8700 8701 8702 8703 8704 
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="TimeZone">
    <title>TimeZone</title>
    <body>
      <p>Sets the time zone for displaying and interpreting time stamps. The default is to use
        whatever the system environment specifies as the time zone. See <xref
D
Docs: Updating postgresql.org references to 9.4  
David Yozie 已提交
8705 
          href="https://www.postgresql.org/docs/9.4/datetime-keywords.html" scope="external"
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
8706 8707 8708 8709 8710 8711 8712 8713 8714 8715 8716 8717 8718 8719 8720 8721 8722 8723 8724 8725 8726 8727 8728 8729 8730 8731 8732 8733 8734 8735 8736 8737 8738 8739 8740 8741 8742 8743 8744 8745 8746 8747 8748 8749 8750 8751 8752 8753 8754 8755 8756 8757 8758 8759 8760 8761 8762 8763 8764 8765 8766 8767 8768 8769 8770 8771 8772 8773 8774 8775 8776 8777 8778 8779 
          format="html"><ph>Date/Time Keywords</ph></xref> in the PostgreSQL documentation.</p>
      <table id="TimeZone_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">time zone abbreviation</entry>
              <entry colname="col2"/>
              <entry colname="col3">local<p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="timezone_abbreviations">
    <title>timezone_abbreviations</title>
    <body>
      <p>Sets the collection of time zone abbreviations that will be accepted by the server for date
        time input. The default is <codeph>Default</codeph>, which is a collection that works in
        most of the world. <codeph>Australia</codeph> and <codeph>India</codeph>, and other
        collections can be defined for a particular installation. Possible values are names of
        configuration files stored in <codeph>$GPHOME/share/postgresql/timezonesets/</codeph>. </p>
      <p>To configure Greenplum Database to use a custom collection of timezones, copy the file that
        contains the timezone definitions to the directory
          <codeph>$GPHOME/share/postgresql/timezonesets/</codeph> on the Greenplum Database master
        and segment hosts. Then set value of the server configuration parameter
          <codeph>timezone_abbreviations</codeph> to the file. For example, to use a file
          <codeph>custom</codeph> that contains the default timezones and the WIB (Waktu Indonesia
        Barat) timezone. </p>
      <ol id="ol_u51_pdb_rr">
        <li>Copy the file <codeph>Default</codeph> from the directory
            <codeph>$GPHOME/share/postgresql/timezonesets/</codeph> the file
          <codeph>custom</codeph>. Add the WIB timezone information from the file
            <codeph>Asia.txt</codeph> to the <codeph>custom</codeph>. </li>
        <li>Copy the file <codeph>custom</codeph> to the directory
            <codeph>$GPHOME/share/postgresql/timezonesets/</codeph> on the Greenplum Database master
          and segment hosts.</li>
        <li>Set value of the server configuration parameter <codeph>timezone_abbreviations</codeph>
          to <codeph>custom</codeph>.</li>
        <li>Reload the server configuration file (<codeph>gpstop -u</codeph>).</li>
      </ol>
      <table id="timezone_abbreviations_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">string</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
H
Clean up max, flags, and docs of 'track_activity_query_size' setting.  
Heikki Linnakangas 已提交
8780 8781 8782 
  <topic id="track_activity_query_size">
    <title>track_activity_query_size</title>
    <body>
M
Changed references to current_query to query for pg_stat_activity change (#8756)  
Mel Kiyama 已提交
8783 8784 
      <p>Sets the maximum length limit for the query text stored in <codeph>query</codeph> column of
        the system catalog view <i>pg_stat_activity</i>. The minimum length is 1024 characters. </p>
H
Clean up max, flags, and docs of 'track_activity_query_size' setting.  
Heikki Linnakangas 已提交
8785 8786 8787 8788 8789 8790 8791 8792 8793 8794 8795 8796 8797 8798 8799 8800 8801 8802 8803 8804 
      <table id="track_activity_query_size_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer</entry>
              <entry colname="col2">1024</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
8805 8806 8807 8808 8809 8810 8811 8812 8813 8814 8815 8816 8817 8818 8819 8820 8821 8822 8823 8824 8825 8826 8827 8828 8829 8830 8831 8832 8833 8834 8835 8836 8837 8838 8839 8840 8841 8842 8843 8844 8845 8846 8847 8848 8849 8850 8851 8852 8853 8854 8855 8856 8857 8858 8859 8860 8861 8862 8863 8864 8865 8866 8867 8868 8869 8870 8871 8872 8873 8874 8875 8876 8877 8878 8879 8880 8881 8882 8883 8884 8885 8886 8887 8888 8889 8890 8891 8892 8893 8894 8895 8896 8897 8898 8899 8900 8901 8902 8903 8904 8905 8906 8907 8908 8909 8910 8911 8912 8913 8914 8915 8916 8917 8918 8919 8920 8921 8922 8923 8924 8925 8926 8927 8928 8929 8930 8931 8932 8933 8934 8935 8936 8937 8938 8939 8940 8941 8942 8943 8944 8945 8946 8947 8948 8949 8950 8951 8952 8953 8954 8955 8956 8957 8958 8959 8960 8961 8962 8963 8964 8965 8966 8967 8968 8969 8970 8971 8972 8973 8974 8975 8976 8977 8978 8979 8980 8981 8982 8983 8984 8985 8986 8987 8988 8989 8990 8991 8992 8993 8994 8995 8996 8997 8998 8999 9000 9001 9002 9003 9004 9005 9006 9007 9008 9009 9010 9011 9012 9013 9014 9015 9016 9017 9018 9019 9020 9021 9022 9023 9024 9025 9026 9027 9028 9029 9030 9031 9032 9033 9034 9035 9036 9037 9038 9039 9040 9041 9042 9043 9044 9045 9046 9047 9048 9049 9050 9051 9052 9053 9054 9055 9056 9057 9058 9059 9060 9061 9062 9063 9064 9065 9066 9067 9068 9069 9070 9071 9072 9073 9074 9075 9076 9077 9078 9079 9080 9081 9082 9083 9084 9085 9086 9087 9088 9089 9090 9091 9092 9093 9094 9095 9096 9097 9098 9099 9100 9101 9102 9103 9104 9105 9106 9107 9108 9109 9110 9111 9112 9113 9114 9115 9116 9117 9118 9119 9120 9121 9122 9123 9124 9125 9126 9127 9128 9129 9130 9131 9132 9133 9134 9135 9136 9137 9138 9139 9140 9141 9142 9143 9144 9145 9146 9147 9148 9149 9150 9151 9152 
      </table>
    </body>
  </topic>
  <topic id="transaction_isolation">
    <title>transaction_isolation</title>
    <body>
      <p>Sets the current transaction's isolation level.</p>
      <table id="transaction_isolation_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">read committed<p>serializable</p></entry>
              <entry colname="col2">read committed</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="transaction_read_only">
    <title>transaction_read_only</title>
    <body>
      <p>Sets the current transaction's read-only status.</p>
      <table id="transaction_read_only_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="transform_null_equals">
    <title>transform_null_equals</title>
    <body>
      <p>When on, expressions of the form expr = NULL (or NULL = expr) are treated as expr IS NULL,
        that is, they return true if expr evaluates to the null value, and false otherwise. The
        correct SQL-spec-compliant behavior of expr = NULL is to always return null (unknown).</p>
      <table id="transform_null_equals_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="unix_socket_directory">
    <title>unix_socket_directory</title>
    <body>
      <p>Specifies the directory of the UNIX-domain socket on which the server is to listen for
        connections from client applications.</p>
      <table id="unix_socket_directory_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">directory path</entry>
              <entry colname="col2">unset</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="unix_socket_group">
    <title>unix_socket_group</title>
    <body>
      <p>Sets the owning group of the UNIX-domain socket. By default this is an empty string, which
        uses the default group for the current user. </p>
      <table id="unix_socket_group_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">UNIX group name</entry>
              <entry colname="col2">unset</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="unix_socket_permissions">
    <title>unix_socket_permissions</title>
    <body>
      <p>Sets the access permissions of the UNIX-domain socket. UNIX-domain sockets use the usual
        UNIX file system permission set. Note that for a UNIX-domain socket, only write permission
        matters.</p>
      <table id="unix_socket_permissions_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">numeric UNIX file permission mode (as accepted by the
                  <i>chmod</i> or <i>umask</i> commands)</entry>
              <entry colname="col2">511</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="update_process_title">
    <title>update_process_title</title>
    <body>
      <p>Enables updating of the process title every time a new SQL command is received by the
        server. The process title is typically viewed by the <codeph>ps</codeph> command.</p>
      <table id="update_process_title_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">on</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="vacuum_cost_delay">
    <title>vacuum_cost_delay</title>
    <body>
      <p>The length of time that the process will sleep when the cost limit has been exceeded. 0
        disables the cost-based vacuum delay feature.</p>
      <table id="vacuum_cost_delay_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">milliseconds &lt; 0 (in multiples of 10)</entry>
              <entry colname="col2">0</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="vacuum_cost_limit">
    <title>vacuum_cost_limit</title>
    <body>
      <p>The accumulated cost that will cause the vacuuming process to sleep.</p>
      <table id="vacuum_cost_limit_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer &gt; 0</entry>
              <entry colname="col2">200</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="vacuum_cost_page_dirty">
    <title>vacuum_cost_page_dirty</title>
    <body>
      <p>The estimated cost charged when vacuum modifies a block that was previously clean. It
        represents the extra I/O required to flush the dirty block out to disk again.</p>
      <table id="vacuum_cost_page_dirty_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer &gt; 0</entry>
              <entry colname="col2">20</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="vacuum_cost_page_hit">
    <title>vacuum_cost_page_hit</title>
    <body>
      <p>The estimated cost for vacuuming a buffer found in the shared buffer cache. It represents
        the cost to lock the buffer pool, lookup the shared hash table and scan the content of the
        page.</p>
      <table id="vacuum_cost_page_hit_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer &gt; 0</entry>
              <entry colname="col2">1</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="vacuum_cost_page_miss">
    <title>vacuum_cost_page_miss</title>
    <body>
      <p>The estimated cost for vacuuming a buffer that has to be read from disk. This represents
        the effort to lock the buffer pool, lookup the shared hash table, read the desired block in
        from the disk and scan its content.</p>
      <table id="vacuum_cost_page_miss_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer &gt; 0</entry>
              <entry colname="col2">10</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="vacuum_freeze_min_age">
    <title>vacuum_freeze_min_age</title>
    <body>
      <p>Specifies the cutoff age (in transactions) that <codeph>VACUUM</codeph> should use to
        decide whether to replace transaction IDs with <i>FrozenXID</i> while scanning a table.</p>
      <p>For information about <codeph>VACUUM</codeph> and transaction ID management, see "Managing
        Data" in the <cite>Greenplum Database Administrator Guide</cite> and the <xref
D
Docs: Updating postgresql.org references to 9.4  
David Yozie 已提交
9153 
          href="https://www.postgresql.org/docs/9.4/routine-vacuuming.html#VACUUM-FOR-WRAPAROUND"
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
9154 9155 9156 9157 9158 9159 9160 9161 9162 9163 9164 9165 9166 9167 9168 9169 9170 9171 9172 9173 9174 9175 9176 9177 9178 9179 9180 9181 9182 9183 9184 9185 9186 
          scope="external" format="html">PostgreSQL documentation</xref>.</p>
      <table id="vacuum_freeze_min_age_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer 0-100000000000</entry>
              <entry colname="col2">100000000</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="validate_previous_free_tid">
    <title>validate_previous_free_tid</title>
    <body>
      <p>Enables a test that validates the free tuple ID (TID) list. The list is maintained and used
        by Greenplum Database. Greenplum Database determines the validity of the free TID list by
        ensuring the previous free TID of the current free tuple is a valid free tuple. The default
        value is <codeph>true</codeph>, enable the test.</p>
      <p>If Greenplum Database detects a corruption in the free TID list, the free TID list is
        rebuilt, a warning is logged, and a warning is returned by queries for which the check
D
Removing pivotal references (#2619)  
David Yozie 已提交
9187 
        failed. Greenplum Database attempts to execute the queries. </p>
C
Docs gss rename (#2761)  
Chuck Litzell 已提交
9188 
      <note otherprops="pivotal">If a warning is returned, please contact Pivotal Support.</note>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
9189 9190 9191 9192 9193 9194 9195 9196 9197 9198 9199 9200 9201 9202 9203 
      <table id="table_fkc_4pb_1w">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
M
docs: Add guc verify_gpfdists_cert (#4851)  
Mel Kiyama 已提交
9204 9205 9206 9207 9208 9209 9210 9211 9212 9213 9214 9215 9216 9217 9218 9219 9220 9221 9222 9223 9224 9225 9226 9227 9228 9229 
              <entry colname="col2">true</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="verify_gpfdists_cert">
    <title>verify_gpfdists_cert</title>
    <body>
      <p dir="ltr">When a Greenplum Database external table is defined with the
          <codeph>gpfdists</codeph> protocol to use SSL security, this parameter controls whether
        SSL certificate authentication is enabled. The default is <codeph>true</codeph>, SSL
        authentication is enabled when Greenplum Database communicates with the
          <codeph>gpfdist</codeph> utility to either read data from or write data to an external
        data source.</p>
      <p>The value <codeph>false</codeph> disables SSL certificate authentication. These SSL
        exceptions are ignored:<ul id="ul_ygd_1lj_mdb">
          <li>The self-signed SSL certificate that is used by <codeph>gpfdist</codeph> is not
            trusted by Greenplum Database.</li>
          <li>The host name contained in the SSL certificate does not match the host name that is
            running <codeph>gpfdist</codeph>.</li>
        </ul></p>
      <p>You can set the value to <codeph>false</codeph> to disable authentication when testing the
        communication between the Greenplum Database external table and the <codeph>gpfdist</codeph>
M
docs - ANALYZE command - HLL statistics, incremental analyze (#5696)  
Mel Kiyama 已提交
9230 9231 9232 
        utility that is serving the external data.
        <note type="warning">Disabling SSL certificate authentication exposes a security risk by not
          validating the <codeph>gpfdists</codeph> SSL certificate. </note></p>
M
docs: Add guc verify_gpfdists_cert (#4851)  
Mel Kiyama 已提交
9233 9234 9235 
      <p>For information about the <codeph>gpfdists</codeph> protocol, see <xref
          href="../../admin_guide/external/g-gpfdists-protocol.xml">gpfdists:// Protocol</xref>. For
        information about running the <codeph>gpfdist</codeph> utility, see <xref
L
docs - combine mgmt and client utilities into single section (#8761)  
Lisa Owen 已提交
9236 
          href="../../utility_guide/ref/gpfdist.xml"/>. </p>
M
docs: Add guc verify_gpfdists_cert (#4851)  
Mel Kiyama 已提交
9237 9238 9239 9240 9241 9242 9243 9244 9245 9246 9247 9248 9249 9250 9251 
      <table id="table_ncx_n1h_ldb">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
9252 9253 9254 9255 9256 9257 9258 9259 9260 9261 9262 9263 9264 9265 9266 9267 9268 9269 9270 9271 9272 9273 9274 9275 9276 9277 9278 9279 9280 9281 9282 9283 9284 9285 9286 9287 9288 9289 9290 9291 9292 9293 9294 9295 9296 9297 9298 9299 9300 9301 9302 9303 9304 9305 9306 9307 9308 9309 9310 9311 9312 9313 9314 9315 9316 9317 9318 9319 9320 9321 9322 9323 9324 9325 
              <entry colname="col2">true</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="vmem_process_interrupt">
    <title>vmem_process_interrupt</title>
    <body>
      <p>Enables checking for interrupts before reserving vmem memory for a query during Greenplum
        Database query execution. Before reserving further vmem for a query, check if the current
        session for the query has a pending query cancellation or other pending interrupts. This
        ensures more responsive interrupt processing, including query cancellation requests. The
        default is <codeph>off</codeph>.</p>
      <table id="table_rtz_lyb_tx">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">Boolean</entry>
              <entry colname="col2">off</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="wal_receiver_status_interval">
    <title>wal_receiver_status_interval</title>
    <body>
      <p>For Greenplum Database master mirroring, sets the interval in seconds between
          <codeph>walreceiver</codeph> process status messages that are sent to the active master.
        Under heavy loads, the time might be longer. </p>
      <p>The value of <xref href="#replication_timeout" format="dita"/> controls the time that the
          <codeph>walsender</codeph> process waits for a <codeph>walreceiver</codeph> message.</p>
      <table id="wal_receiver_status_interval_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer 0- INT_MAX/1000</entry>
              <entry colname="col2">10 sec</entry>
              <entry colname="col3">master<p>system</p><p>reload</p><p>superuser</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="writable_external_table_bufsize">
    <title>writable_external_table_bufsize</title>
    <body>
      <p>Size of the buffer (in KB) that Greenplum Database uses for network communication, such as
L
standardize on ... external web table ... (#2300)  
Lisa Owen 已提交
9326 
        the <codeph>gpfdist</codeph> utility and external web tables (that use http). Greenplum
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
9327 9328 9329 9330 9331 9332 9333 9334 9335 9336 9337 9338 9339 9340 9341 9342 9343 9344 
        Database stores data in the buffer before writing the data out. For information about
          <codeph>gpfdist</codeph>, see the <cite>Greenplum Database Utility Guide</cite>.</p>
      <table id="table_writable_external_table_bufsize">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer 32 - 131072 (32KB - 128MB)</entry>
              <entry colname="col2">64</entry>
L
docs - can set writable_external_table_bufize at session level (#4569)  
Lisa Owen 已提交
9345 
              <entry colname="col3">local<p>session</p><p>reload</p></entry>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
9346 9347 9348 9349 9350 9351 9352 9353 9354 9355 9356 9357 9358 9359 9360 9361 9362 9363 9364 9365 9366 9367 9368 9369 9370 9371 9372 9373 9374 9375 9376 9377 9378 9379 9380 9381 9382 9383 9384 9385 9386 9387 9388 9389 9390 9391 9392 9393 9394 9395 9396 9397 9398 9399 9400 9401 9402 9403 9404 9405 9406 9407 9408 9409 
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="xid_stop_limit">
    <title>xid_stop_limit</title>
    <body>
      <p>The number of transaction IDs prior to the ID where transaction ID wraparound occurs. When
        this limit is reached, Greenplum Database stops creating new transactions to avoid data loss
        due to transaction ID wraparound. </p>
      <table id="xid_stop_limit_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer 10000000 - 2000000000</entry>
              <entry colname="col2">1000000000</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="xid_warn_limit">
    <title>xid_warn_limit</title>
    <body>
      <p>The number of transaction IDs prior to the limit specified by <xref href="#xid_stop_limit"
          format="dita"/>. When Greenplum Database reaches this limit, it issues a warning to
        perform a VACUUM operation to avoid data loss due to transaction ID wraparound. </p>
      <table id="xid_warn_limit_table">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">integer 10000000 - 2000000000</entry>
              <entry colname="col2">500000000</entry>
              <entry colname="col3">local<p>system</p><p>restart</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
M
GPDB DOCS - XML gucs xmlbinary, xmloption (#2304)  
mkiyama 已提交
9410 9411 9412 9413 9414 9415 9416 9417 9418 9419 9420 9421 9422 9423 9424 9425 9426 9427 9428 9429 9430 9431 9432 9433 9434 9435 9436 9437 9438 9439 9440 9441 9442 9443 9444 9445 9446 9447 9448 9449 9450 9451 9452 9453 9454 9455 9456 9457 9458 9459 9460 9461 9462 9463 9464 9465 9466 9467 9468 9469 9470 9471 9472 9473 9474 9475 9476 9477 9478 9479 9480 9481 9482 
  <topic id="xmlbinary">
    <title>xmlbinary</title>
    <body>
      <p>Specifies how binary values are encoded in XML data. For example, when
          <codeph>bytea</codeph> values are converted to XML. The binary data can be converted to
        either base64 encoding or hexadecimal encoding. The default is base64.</p>
      <p>The parameter can be set for a database system, an individual database, or a session.</p>
      <table id="table_ph4_5qk_pz">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">base64<p>hex</p></entry>
              <entry colname="col2">base64</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
  <topic id="xmloption">
    <title> xmloption</title>
    <body>
      <p>Specifies whether XML data is to be considered as an XML document
          (<codeph>document</codeph>) or XML content fragment (<codeph>content</codeph>) for
        operations that perform implicit parsing and serialization. The default is
          <codeph>content</codeph>. </p>
      <p>This parameter affects the validation performed by <codeph>xml_is_well_formed()</codeph>.
        If the value is <codeph>document</codeph>, the function checks for a well-formed XML
        document. If the value is <codeph>content</codeph>, the function checks for a well-formed
        XML content fragment.</p>
      <note>An XML document that contains a document type declaration (DTD) is not considered a
        valid XML content fragment. If <codeph>xmloption</codeph> set to <codeph>content</codeph>,
        XML that contains a DTD is not considered valid XML.<p>To cast a character string that
          contains a DTD to the <codeph>xml</codeph> data type, use the <codeph>xmlparse</codeph>
          function with the <codeph>document</codeph> keyword, or change the
            <codeph>xmloption</codeph> value to <codeph>document</codeph>.</p></note>
      <p>The parameter can be set for a database system, an individual database, or a session. The
        SQL command to set this option for a session is also available in Greenplum Database.
        <codeblock>SET XML OPTION { DOCUMENT | CONTENT }</codeblock></p>
      <table id="table_iwq_5qk_pz">
        <tgroup cols="3">
          <colspec colnum="1" colname="col1" colwidth="1*"/>
          <colspec colnum="2" colname="col2" colwidth="1*"/>
          <colspec colnum="3" colname="col3" colwidth="1*"/>
          <thead>
            <row>
              <entry colname="col1">Value Range</entry>
              <entry colname="col2">Default</entry>
              <entry colname="col3">Set Classifications</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry colname="col1">document<p>content</p></entry>
              <entry colname="col2">content</entry>
              <entry colname="col3">master<p>session</p><p>reload</p></entry>
            </row>
          </tbody>
        </tgroup>
      </table>
    </body>
  </topic>
D
Fix for collapsing subnavs (#1712)  
David Yozie 已提交
9483 
</topic>