From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Schanne <michael.schanne@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16461: Segfault in autovacuum process
Date: Tue, 18 Aug 2020 12:20:04 -0400
Message-ID: <1236517.1597767604@sss.pgh.pa.us> (raw)
In-Reply-To: <CAC_kJhTNUSo7NnYZES9V=1pDV0YMZ7n_iLzHORTXe7cDuLrQtg@mail.gmail.com>
References: <CAC_kJhTNUSo7NnYZES9V=1pDV0YMZ7n_iLzHORTXe7cDuLrQtg@mail.gmail.com>
Michael Schanne <michael.schanne@gmail.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, michael.schanne@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16461: Segfault in autovacuum process
In-Reply-To: <1236517.1597767604@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox