Re: BUG #14897: Segfault on statitics SQL request

From: Vincent Lachenal <vincent(dot)lachenal(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14897: Segfault on statitics SQL request
Date: 2017-11-10 19:54:04
Message-ID: CAA2tJ7obkCeGBgyn-2oTL0WPn7EE1M63q++oXfH0ex+n-WSNag@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Sorry. I didn't find the way to create an attachment in the interface.
You can find the database's dump here :
https://github.com/vlachenal/webservices-bench . It is the dump.tar.xz file.

I didn't tweak database. I use default Archlinux configuration (which
should be PostgreSQL default configuration).

I will try to get a stack trace.

Regards.

Vincent

Le ven. 10 nov. 2017 à 20:47, Vincent Lachenal <vincent(dot)lachenal(at)gmail(dot)com>
a écrit :

> Sorry. I didn't find the way to create an attachment in the interface.
> You can find the database dump as attachment.
>
> I didn't tweak database. I use default Archlinux configuration (which
> should be PostgreSQL default configuration).
>
> I will try to get a stack trace.
>
> Regards.
>
> Vincent
>
> Le ven. 10 nov. 2017 à 20:08, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> a écrit :
>
>> vincent(dot)lachenal(at)gmail(dot)com writes:
>> > But one of the resquest I use causes segmentation fault to server
>> process.
>>
>> > The request is :
>> > SELECT
>> > s.protocol,
>> > s.mapper,
>> > c.method,
>> > s.nb_threads,
>> > avg(c.client_end - c.client_start) / 1000000 AS total,
>> > avg(c.server_end - c.server_start) / 1000000 AS server,
>> > avg(c.server_start - c.client_start) / 1000000 AS
>> client_to_server,
>> > avg(c.client_end - c.server_end) / 1000000 AS server_to_client
>> > FROM testsuite s
>> > INNER JOIN testcall c ON s.id = c.test_suite_id
>> > GROUP BY (s.protocol, s.mapper, c.method, s.nb_threads)
>> > ORDER BY s.nb_threads, c.method, s.mapper, s.protocol;
>>
>> The query alone doesn't help us much. Can you put together a
>> self-contained test case, including table declarations and some
>> sample data? Also, are you using any non-default configuration
>> settings?
>>
>> Alternatively, if you can get a stack trace from the crash,
>> that might be enough info to diagnose it (no promises though).
>>
>>
>> https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
>>
>> regards, tom lane
>>
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2017-11-10 20:12:18 Re: BUG #14897: Segfault on statitics SQL request
Previous Message Vincent Lachenal 2017-11-10 19:47:12 Re: BUG #14897: Segfault on statitics SQL request