Invalid input for statement_mem in Pivotal Greenplum - must be less than max_statement_mem

Products

• VMware Tanzu Greenplum

Issue/Introduction

Symptoms:
Master is unable to connect to many segments:

2019-07-19 18:21:25.819584 AEST,"xxxx","xxxx",p562752,th-1470769280,"xxxxx","54568",2019-07-19 18:20:11 AEST,1639142215,con2805447,,seg-
1,,dx11513411,x1639142215,sx1,"LOG","58M01","Master unable to connect to segxxx xxxx:40005 with options FATAL:  Invalid input for statement_
mem. Must be less than max_statement_mem (2048000 kB). (cdbvars.c:1356)",,,,,,"BEGIN",0,,"cdbgang.c",443,

Segment log

2019-07-19 18:20:13.557552 AEST,"xxxx","xxxx",p588346,th-1530185856,"xxxx","37223",2019-07-19 18:20:13 AEST,1127739774,con2805123,,seg-1,,,x1127739774,sx1,"FATAL","XX000","Invalid input for statement_mem. Must be less than max_statement_mem (2048000 kB). (cdbvars.c:1356)",,,,,,,0,,"cdbvars.c",1356,"Stack trace:
1    0xb07a42 postgres <symbol not found> (elog.c:502)
2    0xb09a58 postgres elog_finish (elog.c:1446)
3    0xcd598b postgres gpvars_assign_statement_mem (cdbvars.c:1356)
4    0xb3526a postgres set_config_option (guc.c:10175)
5    0xb37943 postgres ProcessGUCArray (guc.c:12092)
6    0xb203e6 postgres InitPostgres (postinit.c:316)
7    0x99dc9f postgres PostgresMain (postgres.c:4423)
8    0x8fabe9 postgres <symbol not found> (postmaster.c:6672)
9    0x8fd690 postgres PostmasterMain (postmaster.c:7603)
10   0x7fd50f postgres main (main.c:206)
11   0x7f78a0482b35 libc.so.6 __libc_start_main + 0xf5
12   0x4bee79 postgres <symbol not found> + 0x4bee79

Environment

Cause

This is due to the max_statement_mem parameter being only changed from the master instance. While the statement_mem parameter was changed at all instances, this error will show up.

Resolution

Use gpconfig tool to setup max_statement_mem parameter.