From: Tom Lane <tgl@sss.pgh.pa.us>
To: wambacher@posteo.de
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: crash during autovacuum
Date: Fri, 28 Dec 2018 10:26:14 -0500
Message-ID: <21518.1546010774@sss.pgh.pa.us> (raw)
In-Reply-To: <22fb8ec4-67d8-314a-98db-91e2709106db@posteo.de>
References: <22fb8ec4-67d8-314a-98db-91e2709106db@posteo.de>
wambacher@posteo.de writes:
> this morning my database crashed, because of a problem during autovacuum.
> this is the second time during the last 2 month and i can't find out why.
Can you get a stack trace from the crash?
https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
The evidence may be gone by now for your current crash, but if so, make
sure you are prepared to capture info from the next one.
The other respondent might be right that this ultimately traces to
data corruption, but it's hard to be sure without more info.
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-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, wambacher@posteo.de, pgsql-admin@lists.postgresql.org
Subject: Re: crash during autovacuum
In-Reply-To: <21518.1546010774@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