From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | 梁博 <12020405(at)qq(dot)com>, pgsql-sql <pgsql-sql(at)lists(dot)postgresql(dot)org> |
Subject: | Re: backend process was crashed when using zabbix monitor |
Date: | 2019-01-01 01:27:46 |
Message-ID: | CAH2-Wz=a7N0wSNMiAVD5q9eqJMWn4UkgJjN70D26acAtW5j5Pg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Fri, Dec 28, 2018 at 7:36 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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
From | Date | Subject | |
---|---|---|---|
Next Message | 梁博 | 2019-01-01 01:38:22 | Re:Re: backend process was crashed when using zabbix monitor |
Previous Message | 梁博 | 2019-01-01 01:06:57 | Re:Re: backend process was crashed when using zabbix monitor |