Re: [BUGS] BUG #14897: Segfault on statitics SQL request - Mailing list pgsql-bugs

From Tom Lane
Subject Re: [BUGS] BUG #14897: Segfault on statitics SQL request
Date
Msg-id 1415.1510340891@sss.pgh.pa.us
Whole thread Raw
In response to [BUGS] BUG #14897: Segfault on statitics SQL request  (vincent.lachenal@gmail.com)
Responses Re: [BUGS] BUG #14897: Segfault on statitics SQL request  (Vincent Lachenal <vincent.lachenal@gmail.com>)
List pgsql-bugs
vincent.lachenal@gmail.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


--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: vincent.lachenal@gmail.com
Date:
Subject: [BUGS] BUG #14897: Segfault on statitics SQL request
Next
From: Vincent Lachenal
Date:
Subject: Re: [BUGS] BUG #14897: Segfault on statitics SQL request