Hi, On 2018-04-07 21:28:39 +0200, Andreas Seltenreich wrote: > the following query triggers a segfault for me when run against the > regression database. Testing was done with master at 039eb6e92f. > Backtrace below.
Andrew, that looks like it's in your area? > Core was generated by `postgres: smith regression [local] SELECT '. > Program terminated with signal SIGSEGV, Segmentation fault. > (gdb) bt > #0 0x0000556c14759cb8 in expand_tuple > (targetHeapTuple=targetHeapTuple@entry=0x0, > targetMinimalTuple=targetMinimalTuple@entry=0x7ffe8088a118, > sourceTuple=<optimized out>, tupleDesc=<optimized out>) > at heaptuple.c:984 > #1 0x0000556c1475bb46 in minimal_expand_tuple (sourceTuple=<optimized out>, > tupleDesc=<optimized out>) at heaptuple.c:1015 > #2 0x0000556c14917177 in ExecCopySlotMinimalTuple (slot=<optimized out>) at > execTuples.c:631 > #3 0x0000556c14ba8ada in copytup_heap (state=0x556c16c4f5e8, > stup=0x7ffe8088a180, tup=<optimized out>) at tuplesort.c:3585 > #4 0x0000556c14baf8e6 in tuplesort_puttupleslot > (state=state@entry=0x556c16c4f5e8, slot=<optimized out>) at tuplesort.c:1444 > #5 0x0000556c14937791 in ExecSort (pstate=0x556c16c3ac50) at nodeSort.c:112 > #6 0x0000556c1493c6f4 in ExecProcNode (node=0x556c16c3ac50) at > ../../../src/include/executor/executor.h:239 > #7 begin_partition (winstate=winstate@entry=0x556c16c3a6b8) at > nodeWindowAgg.c:1110 > #8 0x0000556c149403aa in ExecWindowAgg (pstate=0x556c16c3a6b8) at > nodeWindowAgg.c:2094 > #9 0x0000556c1490c0ca in ExecProcNode (node=0x556c16c3a6b8) at > ../../../src/include/executor/executor.h:239 Greetings, Andres Freund
