Re: [BUGS] BUG #14897: Segfault on statitics SQL request
От | Tom Lane |
---|---|
Тема | Re: [BUGS] BUG #14897: Segfault on statitics SQL request |
Дата | |
Msg-id | 1415.1510340891@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | [BUGS] BUG #14897: Segfault on statitics SQL request (vincent.lachenal@gmail.com) |
Ответы |
Re: [BUGS] BUG #14897: Segfault on statitics SQL request
|
Список | 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 по дате отправления: