From: Tom Lane <tgl@sss.pgh.pa.us>
To: wambacher@posteo.de
cc: pgsql-admin@lists.postgresql.org
Subject: Re: crash during autovacuum
In-reply-to: <22fb8ec4-67d8-314a-98db-91e2709106db@posteo.de>
References: <22fb8ec4-67d8-314a-98db-91e2709106db@posteo.de>
Comments: In-reply-to wambacher@posteo.de
	message dated "Fri, 28 Dec 2018 11:13:12 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <21517.1546010774.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 28 Dec 2018 10:26:14 -0500
Message-ID: <21518.1546010774@sss.pgh.pa.us>
Precedence: bulk

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