Queries using lateral joins causing segment panic

Products

• VMware Tanzu Greenplum
• VMware Tanzu Greenplum / Gemfire
• VMware Tanzu Data Suite

Issue/Introduction

Lateral joins are an unsupported operation in GPDB 6.x. When running operations using lateral joins, segment PANIC can occur, causing segments to go down in the environment, requiring recovery.

The below error messages on a query using lateral join operations can indicate that this issue has occurred:

Master Logs
"LOG","00000","FTS: cannot establish libpq connection (content=###, dbid=###): server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request.
[...]
NOTICE,""Feature not supported: SIRV functions""

Segment Logs
"PANIC","XX000","Unexpected internal error: Segment process received signal SIGSEGV",,,,,,,0,,,,"1    0x7f66a2eaf8c0 libpthread.so.0 <symbol not found> + 0xa2eaf8c0
2    0x8cd996 postgres <symbol not found> (execQual.c:2220)
...

Environment

Product Version: 6.25

Resolution

As a workaround for this error, queries which make use of lateral joins must be avoided or rewritten.

As of version 6.26.2, the error has been resolved, preventing the queries from resulting in a PANIC.

v6.26.2
370114, 345498
Resolves an issue where passing through parameters by a motion caused the database to panic. The fix prevents external parameters from being passed through.
Release Notes: https://docs.vmware.com/en/VMware-Greenplum/6/greenplum-database/relnotes-release-notes.html#release-6.26.2