"PANIC","XX000","ERRORDATA_STACK_SIZE exceeded

CST,0,con13188,cmd3,seg11,slice4,,,sx1,"PANIC","XX000","ERRORDATA_STACK_SIZE exceeded (elog.c:1679)",,,,,,,0,,"elog.c",1679,"Stack trace:
1 0xbfec27 postgres errstart + 0x267
2 0x6b2ce3 postgres + 0x6b2ce3
3 0xc02866 postgres + 0xc02866
4 0x733904 postgres AbortCurrentTransaction + 0x24
5 0xa96c80 postgres PostgresMain + 0x300
6 0x6b1a63 postgres + 0x6b1a63
7 0xa1c636 postgres PostmasterMain + 0x10a6
8 0x6b5911 postgres main + 0x421
9 0x7fd3ea70ee75 libc.so.6 __libc_start_main + 0xf5
10 0x6c17bc postgres + 0x6c17bc
after error occurred，some segments down

Start with the reported ERRODATA_STACK_SIZE exceeded message and the elog.c:1679 location, then use the supplied stack trace to investigate why segments go down after the error. Done means reproducing the failure, identifying its cause, and verifying a fix; the issue names no test or reproduction steps.

Written by the indexing model from the issue text.