Re: PANIC: could not write to file "pg_wal/xlogtemp.11399": No space left on device

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jason Ralph <jralph(at)affinitysolutions(dot)com>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: PANIC: could not write to file "pg_wal/xlogtemp.11399": No space left on device
Date: 2019-09-13 15:29:45
Message-ID: 24616.1568388585@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Jason Ralph <jralph(at)affinitysolutions(dot)com> writes:
> My question is should I be concerned with data loss when a vacuumdb with analyze crashed due to space, and I restarted the database possibly when it was trying to recover? The hinted message at 2019-09-12 23:26:15.978 in the log scares me a bit.

No, that's unsurprising given that you did a forced shutdown while
recovery from the initial crash was still running. The HINT is
probably not terribly well worded; it really only applies if
recovery crashed, which doesn't seem to be the case here.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ertan Küçükoglu 2019-09-13 15:34:06 No primary key table
Previous Message Paul Jungwirth 2019-09-13 15:19:27 Re: How to handle things that change over time?