| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Schanne <michael(dot)schanne(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16461: Segfault in autovacuum process |
| Date: | 2020-08-18 16:20:04 |
| Message-ID: | 1236517.1597767604@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Michael Schanne <michael(dot)schanne(at)gmail(dot)com> writes:
> I wanted to close the loop on this... after seeing a few other processes
> mysteriously segfault on the same machine, I ran a memory test (memtest86+)
> which found 2 bad memory addresses. I replaced the RAM and had no more
> issues with processes segfaulting. So, this was a hardware issue, not a
> bug in postgresql.
Thanks for following up!
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-08-18 20:09:44 | Re: BUG #16583: merge join on tables with different DB collation behind postgres_fdw fails |
| Previous Message | Michael Schanne | 2020-08-18 16:06:56 | RE: BUG #16461: Segfault in autovacuum process |