| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | "Vitaly V(dot) Voronov" <wizard_1024(at)tut(dot)by>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15144: *** glibc detected *** postgres: postgres smsconsole [local] SELECT: double free or corruption (!pre |
| Date: | 2018-04-16 17:03:40 |
| Message-ID: | 20180416170340.alo53a25f5kus54r@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Peter Geoghegan wrote:
> This now seems unnecessary, since it's already evident from your "bt
> full" output that the query involved in the crash was "select count(*)
> from pg_buffercache where isdirty".
Hmm, so is the Zabbix monitoring running that query frequently?
Because, as I recall, pg_buffercache is pretty heavy on the system,
since it needs to acquire all the bufmgr locks simultaneously?
In other words, this seems a terrible query to be running in zabbix. I
have vague memories of somebody submitting a version of this code that
returned approximate answers, good enough for monitoring ...
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-04-16 17:09:43 | Re: BUG #15144: *** glibc detected *** postgres: postgres smsconsole [local] SELECT: double free or corruption (!pre |
| Previous Message | Peter Geoghegan | 2018-04-16 16:59:50 | Re: BUG #15144: *** glibc detected *** postgres: postgres smsconsole [local] SELECT: double free or corruption (!pre |