Re: BUG #14897: Segfault on statitics SQL request

Vincent Lachenal <vincent.lachenal@gmail.com>

From: Vincent Lachenal <vincent.lachenal@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@postgresql.org
Date: 2017-11-10T19:47:12Z
Lists: pgsql-bugs

Attachments

Sorry. I didn't find the way to create an attachment in the interface.
You can find the database dump as attachment.

I didn't tweak database. I use default Archlinux configuration (which
should be PostgreSQL default configuration).

I will try to get a stack trace.

Regards.

Vincent

Le ven. 10 nov. 2017 à 20:08, Tom Lane <tgl@sss.pgh.pa.us> a écrit :

> 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

  1. Prevent int128 from requiring more than MAXALIGN alignment.

  2. Rearrange c.h to create a "compiler characteristics" section.