GPDB Administrator notes (5) GP System Configuration

In GPDB, the Master and each Segment Instance have their own postgresql. conf files. Parameters
The number of local parameters means that each Segment Instance is obtained according to its own postgresql. conf file.
Take the value of the parameter. For localization parameters, each Instance (Master and Segment) in the system must be)
Configuration.
You can use the gpconfig command to modify parameters in all postgresql. conf files of the GPDB system.
For example:
$ Gpconfig-c gp_vmem_protect_limit-v 4096 MB
Then restart GPDB to make sure the modified configuration takes effect:
$ Gpstop-r
Session-level parameter settings = # SET work_mem TO '200mb ';
= # RESET work_mem;
View master configuration parameter settings [gpadmin @ mdw ~] $ Psql libo-c 'show all ;'
View the system configuration parameters gpconfig [gpadmin @ mdw ~] $ Gpconfig -- show max_connectionsValues on all segments are consistentGUC: max_connectionsMaster value: 250 Segment value: 750
Memory consumption Parameters
These parameters are null in the system memory usage. You can adjust gp_vmem_protect_limit to avoid running
Memory overflow occurs on the Segment host during query processing.
Export gp_vmem_idle_resource_timeout
Export gp_vmem_protect_limit
Export gp_vmem_protect_segworker_cache_limit
 Max_appendonly_tables
 Max_prepared_transactions
 Max_stack_depth
 Shared_buffers
 Temp_buffers