Master segment got PANIC while loading data in GPDB 5.10.x and below

Products

• VMware Tanzu Greenplum

Issue/Introduction

Master received PANIC with the following error while loading data:

2021-05-31 03:16:49.219866 +09|||p165365|th0|||2021-05-24 11:06:27 +09|0|con620|cmd4794|seg-1|||||PANIC: |XX000|Unexpected internal error: Master process received signal SIGSEGV|||||||0||||
1 0x7fb9c2c707e0 libpthread.so.0 <symbol not found> + 0xc2c707e0 
2 0x5b6a42 postgres parse_analyze (analyze.c:168) 
3 0x835269 postgres pg_analyze_and_rewrite + 0x29 
4 0x931e82 postgres RevalidateCachedPlanWithParams + 0x2d2 
5 0x8311ba postgres <symbol not found> (postgres.c:0)

Environment

Product Version: 5.7

Resolution

In some cases when a GPDB client application passes an empty string as a query to GPDB, it generates a PANIC.

This issue has been resolved in GPDB 5.11 and higher versions, it has been enhanced to handle the specified situation when an empty string is passed as a query.

In order to resolve this issue, please upgrade to GPDB 5.11 or higher versions.