Configuration Parameter Categories
Note: If you install and manage HAWQ using Ambari, be aware that property changes made using could be overwritten by Ambari. For Ambari-managed HAWQ clusters, always use the Ambari administration interface to set or change HAWQ configuration properties.
The following parameters configure the append-only tables feature of HAWQ.
Client Connection Default Parameters
These configuration parameters set defaults that are used for client connections.
Locale and Formatting Parameters
Other Client Default Parameters
Connection and Authentication Parameters
These parameters control how clients connect and authenticate to HAWQ.
Connection Parameters
- max_connections
- superuser_reserved_connections
- tcp_keepalives_idle
- unix_socket_directory
- unix_socket_permissions
Security and Authentication Parameters
Database and Tablespace/Filespace Parameters
The following parameters configure the maximum number of databases, tablespaces, and filespaces allowed in a system.
Error Reporting and Logging Parameters
These configuration parameters control HAWQ logging.
Log Rotation
When to Log
What to Log
- debug_pretty_print
- debug_print_parse
- debug_print_prelim_plan
- debug_print_slice_table
- log_connections
- log_dispatch_stats
- log_executor_stats
- log_parser_stats
- log_statement
- log_timezone
- gp_log_format
- gp_reraise_signal
The following parameters configure the external tables feature of HAWQ.
GPORCA Parameters
These parameters control the usage of GPORCA by HAWQ. For information about GPORCA, see About GPORCA.
HAWQ Array Configuration Parameters
Interconnect Configuration Parameters
- gp_interconnect_cache_future_packets
- gp_interconnect_fc_method
- gp_interconnect_min_retries_before_timeout
- gp_interconnect_queue_depth
- gp_interconnect_snd_queue_depth
- gp_interconnect_timer_period
- gp_max_packet_size
Fault Operation Parameters
Filepace Parameters
Master Configuration Parameters
Read-Only Parameters
Segment Configuration Parameters
HAWQ Extension Framework (PXF) Parameters
The parameters in this topic control configuration, query analysis, and statistics collection in the HAWQ Extension Framework (PXF).
HAWQ PL/Java Extension Parameters
The parameters in this topic control the configuration of HAWQ PL/Java extensions.
The following configuration parameters configure the HAWQ resource management feature.
- hawq_re_memory_overcommit_max
- hawq_rm_force_alterqueue_cancel_queued_request
- hawq_rm_memory_limit_perseg
- hawq_rm_nresqueue_limit
- hawq_rm_nvcore_limit_perseg
- hawq_rm_nvseg_perquery_perseg_limit
- hawq_rm_rejectrequest_nseg_limit
- hawq_rm_segment_heartbeat_interval
- hawq_rm_stmt_nvseg
- hawq_rm_tolerate_nseg_limit
- hawq_rm_yarn_app_name
- hawq_rm_yarn_scheduler_address
Lock Management Parameters
These configuration parameters set limits for locks and deadlocks.
Past PostgreSQL Version Compatibility Parameters
The following parameters provide compatibility with older PostgreSQL versions. You do not need to change these parameters in HAWQ.
Query Tuning Parameters
These parameters control aspects of SQL query processing such as query operators and operator settings and statistics sampling.
Legacy Query Optimizer Operator Control Parameters
The following parameters control the types of plan operations the legacy query optimizer can use. Enable or disable plan operations to force the legacy optimizer to choose a different plan. This is useful for testing and comparing query performance using different plan types.
- enable_bitmapscan
- enable_hashagg
- enable_indexscan
- enable_nestloop
- enable_sort
- gp_enable_agg_distinct
- gp_enable_direct_dispatch
- gp_enable_fast_sri
- gp_enable_groupext_distinct_pruning
- gp_enable_predicate_propagation
- gp_enable_sequential_window_plans
- gp_enable_sort_limit
Legacy Query Optimizer Costing Parameters
Warning: Do not adjust these query costing parameters. They are tuned to reflect HAWQ hardware configurations and typical workloads. All of these parameters are related. Changing one without changing the others can have adverse affects on performance.
Database Statistics Sampling Parameters
Aggregate Operator Configuration Parameters
Join Operator Configuration Parameters
Other Legacy Query Optimizer Configuration Parameters
Ranger Configuration Parameters
These parameters control certain aspects of Ranger configuration, including enabling Ranger authorization for HAWQ and the HAWQ Ranger Plug-in Service port setting.
Automatic Statistics Collection
When automatic statistics collection is enabled, you can run ANALYZE
automatically in the same transaction as an , COPY
or CREATE TABLE...AS SELECT
statement when a certain threshold of rows is affected (on_change
), or when a newly generated table has no statistics (on_no_stats
). To enable this feature, set the following server configuration parameters in your HAWQ file by using the hawq config
utility and restart HAWQ:
Runtime Statistics Collection Parameters
These parameters control the server statistics collection feature. When statistics collection is enabled, you can access the statistics data using the pg_stat and pg_statio family of system catalog views.
System Resource Consumption Parameters
These parameters set the limits for system resources consumed by HAWQ.
Memory Consumption Parameters
These parameters control system memory usage. You can adjust hawq_re_memory_overcommit_max
to avoid running out of memory at the segment hosts during query processing. See also HAWQ Resource Management.
Free Space Map Parameters
These parameters control the sizing of the free space map, which contains expired rows. Use VACUUM
to reclaim the free space map disk space.
OS Resource Parameters
Warning: Avoid using cost-based vacuum delay because it runs asynchronously among the segment instances. The vacuum cost limit and delay is invoked at the segment level without taking into account the state of the entire HAWQ array
You can configure the execution cost of VACUUM
and commands to reduce the I/O impact on concurrent database activity. When the accumulated cost of I/O operations reaches the limit, the process performing the operation sleeps for a while, Then resets the counter and continues execution