From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Greg Sabino Mullane <htamfids@gmail.com>
To: pgsql-docs <pgsql-docs@lists.postgresql.org>
Subject: Re: Discourage splitting pg_wal directory
Date: Mon, 18 Mar 2024 16:58:03 +0100
Message-ID: <54e3551994accbe9cf73916b88e2e85dddadd804.camel@cybertec.at> (raw)
In-Reply-To: <CAKAnmmL31OAwXdAe8CCp0URB67cP8fAOHpsdiaoqXbcGOcvy+Q@mail.gmail.com>
References: <CAKAnmmL31OAwXdAe8CCp0URB67cP8fAOHpsdiaoqXbcGOcvy+Q@mail.gmail.com>
On Mon, 2024-03-18 at 11:32 -0400, Greg Sabino Mullane wrote:
> "It is advantageous if the WAL is located on a different disk from the
> main database files. This can be achieved by moving the pg_wal directory
> to another location (while the server is shut down, of course) and
> creating a symbolic link from the original location in the main data
> directory to the new location."
>
> This is not as important as it used to be, and I would even hazard to
> say that we should not be encouraging it. There are still use cases for
> doing so, yes, but "advantageous" is too much. I played with some wording,
> but at the end of the day, I am thinking that we simply remove this
> paragraph entirely.
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.
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: <54e3551994accbe9cf73916b88e2e85dddadd804.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