88 Dec 8 11:22 postgresql.auto.conf -rw------- 1 postgres postgres 20904 Dec 8 11:22 postgresql.conf -rw------- 1 postgres postgres 59 Dec 8 11:30 postmaster.opts -rw------- 1 postgres postgres postgresql-Sat.log -bash-4.1$ 2018年PostgreSQL中国技术大会 微信号：laohouzi999 2.日志的配置 2018年PostgreSQL中国技术大会 微信号：laohouzi999 -bash-4.1$ cat postgresql.conf |egrep -i "Log_directory|Log_statement|Session_preload_librar 3/bin/postgres -D /var/lib/postgresql/9.3/main -c config_file=/etc/postgresql/9.3/main/postgresql.conf 2018年PostgreSQL中国技术大会 微信号：laohouzi999 log_statement = 'none' # none, ddl, mod, all 控制记录哪

...................................................................................... - 31 - 第四章：配置客户端认证 ............................................................................................. .......................................................................................... - 48 - 配置与使用资源组 ............................................................................................ 使用资源队列做资源管理的步骤 ............................................................................ - 71 - 配置资源队列管理资源 ..........................................................................................

Greenplum运维常见问题  Greenplum运维常用命令  Greenplum日常检查和故障处理  Greenplum项目经验分享 内核参数  通常情况下，内核参数按照GPDB安装手册配置，如需要增加连接数支持，以下参数需要增大  kernel.shmmax = 1000000000  kernel.sem = 250 512000 100 2048  Redhat gp_autostats_on_change_threshold 5000000 5000000 gp_vmem_protect_limit 32768（64G内存时，其他配置 依据实际内存进行调整） 16384（64G内存时，其他配置 依据实际内存进行调整） gp_segment_connect_timeout 10min 10min log_min_duration_statement Instance实例数的配置建议 • Instance是GPDB的最小并行单元，每个Segment 节点一般配置4~8个Instance，初始化完成后很 难修改，需要提前规划； • 每个Instance都是一套独立的进程，当客户端 发起一个请求时，每个Instance都将FORK子进 程并行工作； • 对于并发请求高、面向于复杂的灵活查询的系 统，建议每个Segment配置4个或以下Instance，

目录结构，都有各自的一套 Postgresql 数据库守护进 程（甚至可以通过 UT 模式进行单个实例的访问）。正因为如此，甚 至一个运行在单节点上的 GreenplumDB 也是一个小型的并行计算架 构，一般一个节点配置 6~8 个实例，相当于在一个节点上有 6~8 个 Postgresql 数据库同时并行工作，优势在于可以充分利用到每个节点 的所有 CPU 和 IO 能力。 Greenplum 单个节点上运行能力比其它数据库也快很多，如果运行在 同规格的计算服务器，后续扩容也要保证新加机器的性不能低于原有 机器，这是由于 MPP 架构本身存在木桶效应，单台机器的性能短板， 很可能导致整体集群变慢，虽然 Greenplum 可以根据具体的硬件配置， 初始化的时候调整每台计算节点部署的实例数，但从具体实施看，极 少有客户这么做。 Segment 节点推荐采用硬件规格如下：两块万兆网卡（一般多为单网 卡双网口）用于内部互连，1-2 块千兆网卡用于带外管理和接入客户 盘插入到灾备机，由于 RAID 信息写在磁盘上，对调磁盘后，所有 数据信息仍然保留，这样就能避免数据同步带来的性能损耗，这种 方式要求集群所有机器采用相同规格的 RAID 卡。 以下是我们新一代一体机硬件和机柜配置，大家可以参考： Big Date2.indd 27 16-11-22 下午3:38 28 4. ETL 服务器 ETL 服务器是数据的临时存放区，由于 Greenplum 服务器并行加载

Parameters 284 OpenSSL Configuration 284 Creating a Self-Signed Certificate 284 Configuring postgresql.conf for SSL Authentication 285 Configuring the SSL Client Connection 286 PAM-Based Authentication segment postgresql.conf configuration files to serve as defaults when the Greenplum Database system is started. If you delete these assignments from the coordinator and each segment postgresql.conf files the coordinator and/or segment host, but can be changed after initialization by editing the postgresql.conf file of each Greenplum coordinator and segment instance. You can check the active locale settings

Parameters 512 OpenSSL Configuration 513 Creating a Self-Signed Certificate 513 Configuring postgresql.conf for SSL Authentication 514 Configuring the SSL Client Connection 514 PAM-Based Authentication had been initialized using pg_ctl. This was due to the mirror segment port number listed in postgresql.conf being out of sync with the number listed in the gp_segment_configuration table. Data Flow the value of a server configuration parameter(s) comments out any parameter setting in the postgresql.conf file whose name starts with the same text string. 32042 Resolves an issue introduced in Greenplum

Parameters 493 OpenSSL Configuration 493 Creating a Self-Signed Certificate 494 Configuring postgresql.conf for SSL Authentication 494 Configuring the SSL Client Connection 495 VMware Tanzu Greenplum had been initialized using pg_ctl. This was due to the mirror segment port number listed in postgresql.conf being out of sync with the number listed in the gp_segment_configuration table. Data Flow the value of a server configuration parameter(s) comments out any parameter setting in the postgresql.conf file whose name starts with the same text string. 32042 Resolves an issue introduced in Greenplum

Parameters 491 OpenSSL Configuration 491 Creating a Self-Signed Certificate 491 Configuring postgresql.conf for SSL Authentication 492 Configuring the SSL Client Connection 493 PAM-Based Authentication had been initialized using pg_ctl. This was due to the mirror segment port number listed in postgresql.conf being out of sync with the number listed in the gp_segment_configuration table. Data Flow the value of a server configuration parameter(s) comments out any parameter setting in the postgresql.conf file whose name starts with the same text string. 32042 Resolves an issue introduced in Greenplum

Parameters 518 OpenSSL Configuration 518 Creating a Self-Signed Certificate 518 Configuring postgresql.conf for SSL Authentication 519 Configuring the SSL Client Connection 520 PAM-Based Authentication had been initialized using pg_ctl. This was due to the mirror segment port number listed in postgresql.conf being out of sync with the number listed in the gp_segment_configuration table. Data Flow the value of a server configuration parameter(s) comments out any parameter setting in the postgresql.conf file whose name starts with the same text string. 32042 Resolves an issue introduced in Greenplum

Parameters 488 OpenSSL Configuration 489 Creating a Self-Signed Certificate 489 Configuring postgresql.conf for SSL Authentication 490 Configuring the SSL Client Connection 490 PAM-Based Authentication had been initialized using pg_ctl. This was due to the mirror segment port number listed in postgresql.conf being out of sync with the number listed in the gp_segment_configuration table. Data Flow the value of a server configuration parameter(s) comments out any parameter setting in the postgresql.conf file whose name starts with the same text string. 32042 Resolves an issue introduced in Greenplum