Re: backend process was crashed when using zabbix monitor
Peter Geoghegan <[email protected]> Mon, 31 Dec 2018 17:27:46 -0800
| Newsgroups | gmane.comp.db.postgresql.sql |
|---|---|
| Message-ID | <CAH2-Wz=a7N0wSNMiAVD5q9eqJMWn4UkgJjN70D26acAtW5j5Pg@mail.gmail.com> |
On Fri, Dec 28, 2018 at 7:36 AM Tom Lane <[email protected]> wrote: > 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. My guess is the same as it was back in April: tuplestore and/or one of its callers gets confused about some aspect of resource management, leading to a double-free. Last time it was also a view that expands to a function call (pg_buffercache, rather than pg_stat_statements). I have a question for 梁博: Does pgpool happen to be involved here? That was a factor in the bug report back in April. It's not impossible that it's part of the problem here, too. -- Peter Geoghegan