Re: BUG #14683: *** glibc detected *** SELECT: double free or corruption

Ray Warren <Ray(dot)Warren(at)artsalliancemedia(dot)com> writes:
> ======= Backtrace: =========
> /lib64/libc.so.6(+0x75dee)[0x7f1d6ba7edee]
> /lib64/libc.so.6(+0x78ff6)[0x7f1d6ba81ff6]
> /lib64/libc.so.6(+0x7babe)[0x7f1d6ba84abe]
> /lib64/libc.so.6(realloc+0x158)[0x7f1d6ba84f08]
> postgres: postgres etms 172.30.8.63(53338) SELECT[0x7c8d72]
> postgres: postgres etms 172.30.8.63(53338) SELECT(repalloc+0x25)[0x7c9295]
> postgres: postgres etms 172.30.8.63(53338) SELECT(enlargeStringInfo+0x4e)[0x5e505e]
> postgres: postgres etms 172.30.8.63(53338) SELECT(appendStringInfoChar+0x28)[0x5e5178]
> postgres: postgres etms 172.30.8.63(53338) SELECT[0x7a6724]
> postgres: postgres etms 172.30.8.63(53338) SELECT(EmitErrorReport+0xa2f)[0x7a963f]
> postgres: postgres etms 172.30.8.63(53338) SELECT(errfinish+0x8d)[0x7a97dd]
> postgres: postgres etms 172.30.8.63(53338) SELECT(FileClose+0x1c5)[0x6966d5]
> postgres: postgres etms 172.30.8.63(53338) SELECT(BufFileClose+0x32)[0x698652]
> postgres: postgres etms 172.30.8.63(53338) SELECT(ExecHashJoin+0x31b)[0x5ce60b]
> postgres: postgres etms 172.30.8.63(53338) SELECT(ExecProcNode+0x168)[0x5bc9f8]
> postgres: postgres etms 172.30.8.63(53338) SELECT(ExecSort+0xf9)[0x5d86c9]
> postgres: postgres etms 172.30.8.63(53338) SELECT(ExecProcNode+0x148)[0x5bc9d8]

These stack traces would be a lot more useful if you had debug symbols
installed, I think.

This trace is rather unusual because it appears to show FileClose trying to
log something. That would be expected if you have log_temp_files enabled,
but otherwise it would indicate an unexpected failure. More generally,
what nondefault configuration settings are you using, and do you have any
extensions installed?

regards, tom lane