title: openGauss 1.0.1 questions about the max_process_memory parameter
body: <p>Deploy openGauss 1.0.1,
  execute the command gs_install -X /opt/soft/cluster_config_enmo.xml, an error is reported when the database is started during the deployment process (gs_ctl started, datadir is -D “/opt/enmo/openGauss/101/data/dn”) Startup failed,</p>
  <p>check the log and find the following error:
  FATAL:  The value of pre-reserved memory for MOT engine is not reasonable: Request for a maximum of 1677312 KB global memory, and 31
  4368 KB session memory (total of 1991680 KB) is invalid since max_process_memory is 2097152 KB</p>
  <p>View parameter ‘max_process_memory’:</p>
  <pre><code>[omm@enmo dn]$ grep max_process_memory postgresql.conf
  max_process_memory = 2GB
  </code></pre>
  <p>Monitor this parameter when deploying, it seems that the default value is 12GB:</p>
  <pre><code>[root@enmo ~]# grep max_process_memory 
  /opt/enmo/openGauss/101/data/dn/postgresql.conf
  #max_process_memory = 12GB
  </code></pre>
  <p>I would like to ask, what is the setting principle of this parameter, and is there any way to avoid such a startup error without manually adjusting this parameter, so that the installation process (gs_install) can be successfully completed.</p>