diff --git a/gpdb-doc/dita/ref_guide/config_params/guc-list.xml b/gpdb-doc/dita/ref_guide/config_params/guc-list.xml index a248f4abf4f9cda3f6029942b7f988cd4bb268b9..9700247b34c3a9fa1b774885fce3a2855a47cabc 100644 --- a/gpdb-doc/dita/ref_guide/config_params/guc-list.xml +++ b/gpdb-doc/dita/ref_guide/config_params/guc-list.xml @@ -367,6 +367,7 @@
    • +
    • @@ -2841,8 +2842,7 @@ 2097152

    CHECKSUM= TRUE | FALSE

    COMPRESSTYPE= ZLIB | - ZSTD | - QUICKLZ2 | + ZSTD | QUICKLZ2 | RLE_TYPE | NONE

    COMPRESSLEVEL= integer between 0 and 19

    ORIENTATION= ROW | @@ -3445,14 +3445,14 @@ gp_enable_query_metrics -

    Enables collection of query metrics. When query metrics collection is enabled, - Greenplum Database collects metrics during query execution. The default is off.

    -

    After changing this configuration parameter, Greenplum Database must be restarted for the +

    Enables collection of query metrics. When query metrics collection is enabled, Greenplum + Database collects metrics during query execution. The default is off.

    +

    After changing this configuration parameter, Greenplum Database must be restarted for the change to take effect.

    -

    The Greenplum Database metrics collection extension, when enabled, sends the - collected metrics over UDP to a Pivotal Greenplum Command Center agent1.

    - 1 The metrics collection extension is included in Pivotal's commercial - version of Greenplum Database. Pivotal Greenplum Command Center is supported only with +

    The Greenplum Database metrics collection extension, when enabled, sends the collected + metrics over UDP to a Pivotal Greenplum Command Center agent1.

    + 1 The metrics collection extension is included in Pivotal's commercial + version of Greenplum Database. Pivotal Greenplum Command Center is supported only with Pivotal Greenplum Database. @@ -4195,19 +4195,16 @@ gp_instrument_shmem_size -

    The amount of shared memory, in kilobytes, allocated for query metrics. - The default is 5120 and the maximum is 131072. At startup, if - gp_enable_query_metrics 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 - gp_enable_query_metrics configuration parameter is off, - or if the slots are exhausted, the metrics are maintained in local memory - instead of in shared memory.

    +

    The amount of shared memory, in kilobytes, allocated for query metrics. The default is 5120 + and the maximum is 131072. At startup, if gp_enable_query_metrics 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 gp_enable_query_metrics configuration parameter is + off, or if the slots are exhausted, the metrics are maintained in local memory instead of in + shared memory.

    @@ -4224,7 +4221,8 @@ integer 0 - 131072 5120 - master

    system

    restart

     + master

    system

    restart

     +
    @@ -4606,6 +4604,42 @@ + + gp_max_slices + +

    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 0, no maximum value.

    +

    Executing a query that generates a large number of slices might affect Greenplum Database + performance. For example, a query that contains UNION or UNION + ALL operators over several complex views can generate a large number of slices. + You can run EXPLAIN ANALYZE on the query to view slice statistics for the + query.

    + + + + + + + + Value Range + Default + Set Classifications + + + + + 0 - INT_MAX + 0 + master

    session

    reload

     +     + + +
    + +     + gp_motion_cost_per_row diff --git a/gpdb-doc/dita/ref_guide/config_params/guc_category-list.xml b/gpdb-doc/dita/ref_guide/config_params/guc_category-list.xml index 429db41bb5a38764a85b19e291397b2daf327c23..e6877c4f2dd46fe3cc5979a2728e9a6c13292201 100644 --- a/gpdb-doc/dita/ref_guide/config_params/guc_category-list.xml +++ b/gpdb-doc/dita/ref_guide/config_params/guc_category-list.xml @@ -679,6 +679,19 @@ + + Query Plan Execution + +

    Control the query plan execution.

    + + + +

    gp_max_slices

    +     +     +     + +     Error Reporting and Logging Parameters @@ -930,10 +943,10 @@ Query Metrics Collection Parameters -

    These parameters enable and configure query metrics collection. When enabled, - Greenplum Database saves metrics to shared memory during query execution. These - metrics are used by Pivotal Greenplum Command Center, which is included with - Pivotal's commercial version of Greenplum Database.

    +

    These parameters enable and configure query metrics collection. When enabled, Greenplum + Database saves metrics to shared memory during query execution. These metrics are used by + Pivotal Greenplum Command Center, which is included with Pivotal's commercial version of + Greenplum Database.

    diff --git a/gpdb-doc/dita/ref_guide/config_params/guc_config.ditamap b/gpdb-doc/dita/ref_guide/config_params/guc_config.ditamap index 8d895ad104782b9652ef2d0daa7d82516da30e9f..66e5bf2930e8ca3f80a61420ee1767323a8d6467 100644 --- a/gpdb-doc/dita/ref_guide/config_params/guc_config.ditamap +++ b/gpdb-doc/dita/ref_guide/config_params/guc_config.ditamap @@ -144,6 +144,7 @@ +