Le 22/08/2020 à 10:11, Julien Rouhaud a écrit :
> On Fri, Aug 21, 2020 at 4:13 PM Thomas SIMON <tsimon@neteven.com> wrote:
>> Hi Julien,
>>
>> thanks for answering me.
>>
>> The only extension I use is repmgr.
> Ok, this shouldn't be a problem.
>
>> I've tried to use gdb to see something (I don't know if i use it
>> correctly) , below the backtarce :
>>
>> [16:03:13]root@db13:/tmp$ gdb -q -c /tmp/core
>> /usr/lib/postgresql/12/bin/postgres
>> Reading symbols from /usr/lib/postgresql/12/bin/postgres...(no debugging
>> symbols found)...done.
>> [New LWP 177990]
>>
>> warning: Unexpected size of section `.reg-xstate/177990' in core file.
>> [Thread debugging using libthread_db enabled]
>> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
>> Core was generated by `postgres: 12/main: supervision neteven2
>> localhost(34868) SELECT '.
>> Program terminated with signal SIGSEGV, Segmentation fault.
>>
>> warning: Unexpected size of section `.reg-xstate/177990' in core file.
>> #0 0x00005636d2d844f1 in equalTupleDescs ()
>> (gdb)
>> (gdb) bt
>> #0 0x00005636d2d844f1 in equalTupleDescs ()
>> #1 0x00005636d31a65cf in ?? ()
>> #2 0x00005636d31b5fd3 in hash_search_with_hash_value ()
>> #3 0x00005636d31a83b1 in assign_record_type_typmod ()
>> #4 0x00005636d31b4855 in ?? ()
>> #5 0x00005636d31b4b43 in get_expr_result_type ()
>> #6 0x00005636d31b4b7b in get_expr_result_tupdesc ()
>> #7 0x00005636d2e8bcce in get_rte_attribute_is_dropped ()
>> #8 0x00005636d303fc7a in AcquireRewriteLocks ()
>> #9 0x00005636d304039e in ?? ()
>> #10 0x00005636d3043aa2 in QueryRewrite ()
>> #11 0x00005636d307de90 in ?? ()
>> #12 0x00005636d307df70 in pg_analyze_and_rewrite ()
>> #13 0x00005636d307e68f in ?? ()
>> #14 0x00005636d30804ad in PostgresMain ()
>> #15 0x00005636d2d73f00 in ?? ()
>> #16 0x00005636d3006f89 in PostmasterMain ()
>> #17 0x00005636d2d75128 in main ()
>> (gdb) cont
>> The program is not being run.
> Thanks!
>
> I don't see any obvious problem in that code, and that's something
> that didn't change for a long time so I'm starting to think this could
> be some hardware problem. Do you have any alarming messages in your
> system logs and/or dmesg?
I checked again, but found nothing relevant.
From what you say, there is not much we can do, so i'm gonna keep this
in mind, and wait to see if it happens again ...
>
>