Tom Lane
"Simon Riggs" <> writes:
You're absolutely right about the not-knowing when you're out of
issue. However, if the xlog has been written then it is not
but at least acceptable that the checkpoint/bgwriter cannot complete
an already committed txn. It's not the txn which is getting the
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

Search Discussions

Discussion Posts


Follow ups

Related Discussions



site design / logo © 2021 Grokbase