| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | "Vitaly V(dot) Voronov" <wizard_1024(at)tut(dot)by> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, 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 18:35:05 |
| Message-ID: | CAH2-Wz=23xbjBbC26G-jH0nYFJ5t+FjRmPp95KGmTmaU6ifGdg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Apr 16, 2018 at 11:05 AM, Vitaly V. Voronov <wizard_1024(at)tut(dot)by> wrote:
> Hello, Peter.
>
> Pgpool used only from App side at another server.
>
> Zabbix running its queries directly at database server.
Can you reliably crash the server by running "select count(*) from
pg_buffercache where isdirty" from psql?
What work_mem setting does Postgres have when Zabbix runs this query?
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-04-16 18:51:06 | Re: Wrong Results from SP-GiST with Collations |
| Previous Message | Vitaly V. Voronov | 2018-04-16 18:05:37 | Re: BUG #15144: *** glibc detected *** postgres: postgres smsconsole [local] SELECT: double free or corruption (!pre |