Re: BUG #15144: *** glibc detected *** postgres: postgres smsconsole [local] SELECT: double free or corruption (!pre

From: Vitaly V(dot) Voronov <wizard_1024(at)tut(dot)by>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
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 20:22:31
Message-ID: 2472021523910151@web55j.yandex.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hello, Peter.

> Can you reliably crash the server by running "select count(*) from
pg_buffercache where isdirty" from psql?

No.
I run from psql and get answer:
# select count(*) from
pg_buffercache where isdirty;
count
-------
71
(1 row)

> What work_mem setting does Postgres have when Zabbix runs this query?
work_mem=64MB

16.04.2018, 21:35, "Peter Geoghegan" <pg(at)bowt(dot)ie>:
> 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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2018-04-16 20:25:21 BUG #15157: Missing icons
Previous Message Peter Geoghegan 2018-04-16 19:58:52 Re: Wrong Results from SP-GiST with Collations