On Tue, 26 May 2020 at 21:53, PG Bug reporting form
<noreply@postgresql.org> wrote:
> Core was generated by `postgres: autovacuum worker process postgres '.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0 0x0000555c1183877b in pfree ()
> I attempted to reproduce the issue with a manual "ANALYZE" of the table in
> question, but it did not segfault again.
That does not really mean that autovacuum is to blame. Both
autovacuum analyze and manual ANALYZE just take random samples of rows
to include in the statistics. You may just not have hit the same rows
with the manual ANALYZE as autovacuum did.
I'd suggest checking that you can read all rows and columns from the
table without getting a crash.
So, providing you can tolerate another crash, you could do:
COPY myschema.mytable TO stdout;
If that crashes then it seems unlikely that what autovacuum is doing
is to blame for your issue. Or if the table is large then you might
want to try pg_dump.
> Please let me know if there is any additional information I can provide for
> this.
It would be good if you could report back to mention if the COPY
crashed the server again or if it worked without any error.
David