Re: BUG #14897: Segfault on statitics SQL request

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: vincent(dot)lachenal(at)gmail(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14897: Segfault on statitics SQL request
Date: 2017-11-10 19:08:11
Message-ID: 1415.1510340891@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Vincent Lachenal 2017-11-10 19:47:12 Re: BUG #14897: Segfault on statitics SQL request
Previous Message vincent.lachenal 2017-11-10 18:57:47 BUG #14897: Segfault on statitics SQL request