From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Greg Sabino Mullane <htamfids@gmail.com>
Cc: pgsql-docs <pgsql-docs@lists.postgresql.org>
Subject: Re: Discourage splitting pg_wal directory
Date: Tue, 19 Mar 2024 18:50:52 +0100
Message-ID: <67be0e7b3067a7db3a475e1c627bfdd79ab50846.camel@cybertec.at> (raw)
In-Reply-To: <CAKAnmmK1_igr8snfjVOHFiTBz1Nc=FBOsLGvKZNzvNmpZdAwdQ@mail.gmail.com>
References: <CAKAnmmL31OAwXdAe8CCp0URB67cP8fAOHpsdiaoqXbcGOcvy+Q@mail.gmail.com>
<54e3551994accbe9cf73916b88e2e85dddadd804.camel@cybertec.at>
<CAKAnmmK1_igr8snfjVOHFiTBz1Nc=FBOsLGvKZNzvNmpZdAwdQ@mail.gmail.com>
On Tue, 2024-03-19 at 11:04 -0400, Greg Sabino Mullane wrote:
> On Mon, Mar 18, 2024 at 11:58 AM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
> > I think it is still a good idea to put data files and WAL on different file
> > systems. Perhaps not so much with the intention of distributing I/O across
> > different disks, but to prevent the data files from filling the WAL disk.
>
> Cannot say I understand this - if the data files are crowding out the WAL,
> surely they are moments away from filling the disk on their own. Disk is cheap
> these days, so I'm not a fan of encouraging complexity if not needed.
If you run out of disk on the data files, you get an error and life goes on.
If WAL runs out of disk space, PostgreSQL will crash.
Yours,
Laurenz Albe
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: pgsql-docs@postgresql.org
Cc: laurenz.albe@cybertec.at, htamfids@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: Discourage splitting pg_wal directory
In-Reply-To: <67be0e7b3067a7db3a475e1c627bfdd79ab50846.camel@cybertec.at>
* 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