public inbox for [email protected]
help / color / mirror / Atom feedFrom: Laurenz Albe <[email protected]>
To: Ron Johnson <[email protected]>
To: Pgsql-admin <[email protected]>
Subject: Re: Postgresql Database and PG_WAL locations
Date: Mon, 02 Sep 2024 15:38:17 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CANzqJaCy8W2m3SunnzXn2tRf-K34=-QFFzRkBdci+-S=9O2smg@mail.gmail.com>
References: <CABHPps4uW9RFwUc0_2CoPMZ1_Du8HRuvNwyXRvCp48ZzgUuKzQ@mail.gmail.com>
<[email protected]>
<CANzqJaBPFm5wjGRuzC8Ywh1=uaeg4BRunhFGgruoy1e-ZxR2Cw@mail.gmail.com>
<[email protected]>
<CANzqJaCy8W2m3SunnzXn2tRf-K34=-QFFzRkBdci+-S=9O2smg@mail.gmail.com>
On Mon, 2024-09-02 at 09:15 -0400, Ron Johnson wrote:
> > but it is still a good idea to separate data and WAL,
> > so that they cannot fill up each other's file system.
>
> Regular checkpoints, transactions(*) that don't stay open for hours
> or days, and monitoring replication to ensure that it keeps replicating
> data instead of piling up on the primary server all solve that problem
Right, if everything is working as it should, monitoring is in place
etc. this will never happen.
But I believe that paranoia is a virtue for the DBA, and it is better
to have a second line of defense than a crash of the database.
> Honestly... it's been YEARSÂ since I've seen that problem.
I see it all the time (on systems I didn't set up).
Yours,
Laurenz Albe
view thread (8+ messages)
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 using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Postgresql Database and PG_WAL locations
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox