| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | 梁博 <12020405(at)qq(dot)com> |
| Cc: | pgsql-sql <pgsql-sql(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: backend process was crashed when using zabbix monitor |
| Date: | 2018-12-28 15:36:45 |
| Message-ID: | 21936.1546011405@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
"=?utf-8?B?5qKB5Y2a?=" <12020405(at)qq(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 梁博 | 2019-01-01 01:06:57 | Re:Re: backend process was crashed when using zabbix monitor |
| Previous Message | 梁博 | 2018-12-28 10:31:51 | backend process was crashed when using zabbix monitor |