From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | fabris(at)colliniconsulting(dot)it |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #14475: buffer overflow and segmentation fault |
Date: | 2016-12-24 00:19:15 |
Message-ID: | 2103.1482538755@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
fabris(at)colliniconsulting(dot)it writes:
> Hi, not sure if the root cause is posgres or bulkload. All I have are lines
> of log
> The failed query runs ( usually ) regularly several time a day
Can't do anything about this with this level of detail, although I'd
suggest that the backtrace tends to point the finger at pg_bulkload:
> /lib64/libc.so.6(__fortify_fail+0x37)[0x7feb01837597]
> /lib64/libc.so.6(+0x10c750)[0x7feb01835750]
> /lib64/libc.so.6(+0x10e507)[0x7feb01837507]
> /usr/pgsql-9.6/lib/pg_bulkload.so(+0x15ef6)[0x7feaedc86ef6]
> /usr/pgsql-9.6/lib/pg_bulkload.so(+0x12b8b)[0x7feaedc83b8b]
> /usr/pgsql-9.6/lib/pg_bulkload.so(pg_bulkload+0x615)[0x7feaedc7f1a5]
If you can get a more symbolic trace it would doubtless help the
pg_bulkload crew analyze this. See advice about adding symbols at
https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2016-12-24 00:53:48 | Re: BUG #14475: buffer overflow and segmentation fault |
Previous Message | Keith Fiske | 2016-12-23 23:21:04 | Re: 9.6rc1 Background worker starting multiple times |