From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | hko(at)framelogic(dot)pl, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #16704: Segmentation Problem - SSL SYSCALL error: EOF detected |
Date: | 2020-11-06 03:18:21 |
Message-ID: | CA+hUKGKWSMpVhx2sSSxAdqY_ge7Q0BQbp7PRkZnwfJUpyNbQWA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Fri, Nov 6, 2020 at 3:40 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> On Fri, Nov 06, 2020 at 10:14:56AM +0900, Michael Paquier wrote:
> > Hard to tell if that's the same issue based on the amount of
> > information given. Providing a stack trace would help:
> > https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows
> >
> > A self-contained test case is also nice to have. Based on the query
> > given anybody looking at this report has to guess what is the schema
> > used in your application.
>
> Another thing that would be really helpful is to know the version of
> OpenSSL you have here. It could be possible that this reflects an
> error triggered internally by OpenSSL.
I guess the Debian version is better for this:
https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD
Also, could we please see the query plan? (EXPLAIN SELECT ...)
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2020-11-06 03:22:19 | Re: SnapBuildSerialize function forgot pfree variable ondisk_c |
Previous Message | PG Bug reporting form | 2020-11-06 03:17:02 | BUG #16705: Triggers deferred during commit callback are not executed |