Re: BUG #14897: Segfault on statitics SQL request
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: vincent.lachenal@gmail.com
Cc: pgsql-bugs@postgresql.org
Date: 2017-11-10T19:08:11Z
Lists: 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
Commits
-
Prevent int128 from requiring more than MAXALIGN alignment.
- d4e38489f98a 9.5.11 landed
- 619a8c47da72 10.2 landed
- 4a15f87d2277 9.6.7 landed
- 7518049980be 11.0 landed
-
Rearrange c.h to create a "compiler characteristics" section.
- cfc157078f2e 9.5.11 landed
- a8910506757c 10.2 landed
- 6c35b3aa465e 9.6.7 landed
- 91aec93e6089 11.0 landed