Re: Out of space situation and WAL log pre-allocation (was Tablespaces)

Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> "Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> > You're absolutely right about the not-knowing when you're out of
space
> > issue. However, if the xlog has been written then it is not
desirable,
> > but at least acceptable that the checkpoint/bgwriter cannot complete
on
> > an already committed txn. It's not the txn which is getting the
error,
> > that's all.
>
> Right. This is in fact not a fatal situation, as long as you don't
run
> out of preallocated WAL space.

...following on also from thoughts on [PERFORM] list...

Clearly running out of pre-allocated WAL space is likely to be the next
issue. Running out of space in the first place is likely to be because
of an intense workload, which is exactly the thing which also makes you
run out of pre-allocated WAL space. Does that make sense?

Best regards, Simon Riggs