| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | hko(at)framelogic(dot)pl, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16704: Segmentation Problem - SSL SYSCALL error: EOF detected |
| Date: | 2020-11-06 01:14:56 |
| Message-ID: | 20201106011456.GF21123@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Nov 05, 2020 at 12:07:38PM +0000, PG Bug reporting form wrote:
> After VACUUM FULL ANALYZE my table, i executed once again my query and query
> result was succes. It has been working about 25 minuts and then i got the
> same error.
>
> Problem is very similar like
> https://www.postgresql.org/message-id/15219.1541773523%40sss.pgh.pa.us
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.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2020-11-06 02:40:34 | Re: BUG #16704: Segmentation Problem - SSL SYSCALL error: EOF detected |
| Previous Message | Burgess, Freddie | 2020-11-05 21:19:17 | pg_dump error attempting to upgrade from PostgreSQL 10 to PostgreSQL 12 |