From: Tom Lane <tgl@sss.pgh.pa.us>
To: vincent.lachenal@gmail.com
cc: pgsql-bugs@postgresql.org
Subject: Re: BUG #14897: Segfault on statitics SQL request
In-reply-to: <20171110185747.31519.28038@wrigleys.postgresql.org>
References: <20171110185747.31519.28038@wrigleys.postgresql.org>
Comments: In-reply-to vincent.lachenal@gmail.com
	message dated "Fri, 10 Nov 2017 18:57:47 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1414.1510340891.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 10 Nov 2017 14:08:11 -0500
Message-ID: <1415.1510340891@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-bugs-owner@postgresql.org

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 =3D 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_b=
ackend

			regards, tom lane


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