pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Paquier <michael@paquier.xyz>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: hargudekishor@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18025: Probably we need to change behaviour of the checkpoint failures in PG
Date: Mon, 17 Jul 2023 17:06:15 +0900
Message-ID: <ZLT2d0b/Zhhgh3v1@paquier.xyz> (raw)
In-Reply-To: <ca4cdccd0b085cbbf10577be4cb05eae4c35a141.camel@cybertec.at>
References: <18025-85e7e63f3ff93d40@postgresql.org>
	<ca4cdccd0b085cbbf10577be4cb05eae4c35a141.camel@cybertec.at>

On Mon, Jul 17, 2023 at 09:53:32AM +0200, Laurenz Albe wrote:
> On Mon, 2023-07-17 at 05:03 +0000, PG Bug reporting form wrote:
>> Scenario is like, there was checkpoint operation failures going on the DB
>> server since last 8 hours which means no successful checkpoint happened in
>> the DB server since last 8 hours. Then DB server went into the crash mode
>> due to the exhausted disk space and did not came up as part of crash
>> recovery.
> 
> Mistake #1: you did not monitor disk space.

max_wal_size is a very critical piece to adjust.  It is usually
recommended to split pg_wal/ into its own partition so as the space
allocated for WAL records is predictable across checkpoints.  This is
not a perfect science as max_wal_size is a soft limit so usually one
needs an extra margin with a WAL partition.  There have been some
patches floating around to make that a hard limit, as well, but I
don't think we've ever agreed on the semantics that would be
acceptable when reaching the upper limit authorized.
--
Michael

Attachments:

  signature.asc (application/pgp-signature, 832B) download

view thread (3+ messages)

Message-ID: <ZLT2d0b/Zhhgh3v1@paquier.xyz>
Permalink:  ../ZLT2d0b%2FZhhgh3v1@paquier.xyz/
Also on:    postgresql.org/message-id/ZLT2d0b/Zhhgh3v1@paquier.xyz

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: michael@paquier.xyz, laurenz.albe@cybertec.at, hargudekishor@gmail.com
  Subject: Re: BUG #18025: Probably we need to change behaviour of the checkpoint failures in PG
  In-Reply-To: <ZLT2d0b/Zhhgh3v1@paquier.xyz>
  References: <18025-85e7e63f3ff93d40@postgresql.org> <ca4cdccd0b085cbbf10577be4cb05eae4c35a141.camel@cybertec.at> <ZLT2d0b/Zhhgh3v1@paquier.xyz>

* 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