agora inbox for pgsql-sql@postgresql.org
help / color / mirror / Atom feedFrom: Tom Lane <tgl@sss.pgh.pa.us>
To: 梁博 <12020405@qq.com>
Cc: pgsql-sql <pgsql-sql@lists.postgresql.org>
Subject: Re: backend process was crashed when using zabbix monitor
Date: Fri, 28 Dec 2018 10:36:45 -0500
Message-ID: <21936.1546011405@sss.pgh.pa.us> (raw)
In-Reply-To: <tencent_48AC33BA0B9814B47D6047711E9D500A3907@qq.com>
References: <tencent_48AC33BA0B9814B47D6047711E9D500A3907@qq.com>
"=?utf-8?B?5qKB5Y2a?=" <12020405@qq.com> writes:
> [ abort trap inside malloc_printerr ]
It looks like glibc noticed corruption of malloc's data structures, which
implies that something inside the server overwrote memory it shouldn't
have ... but just where the bug is is impossible to say from this info.
Do you use any other PG extensions besides pg_stat_statements? Our
usual experience is that extensions have more bugs than the core server,
though in any one case that could be wrong.
It would be worth updating to current (9.6.11) just on general principles.
I'm too lazy to check the release notes to see whether we fixed any
memory-stomp bugs since 9.6.8, but we've certainly fixed many bugs since
then.
regards, tom lane
view thread (5+ messages) latest in thread
Message-ID: <21936.1546011405@sss.pgh.pa.us>
Permalink: ../21936.1546011405@sss.pgh.pa.us/
Also on: postgresql.org/message-id/21936.1546011405@sss.pgh.pa.us
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, 12020405@qq.com, pgsql-sql@lists.postgresql.org
Subject: Re: backend process was crashed when using zabbix monitor
In-Reply-To: <21936.1546011405@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox