Re: Discourage splitting pg_wal directory

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
Cc: pgsql-docs <pgsql-docs(at)lists(dot)postgresql(dot)org>
Subject: Re: Discourage splitting pg_wal directory
Date: 2024-03-19 17:50:52
Message-ID: 67be0e7b3067a7db3a475e1c627bfdd79ab50846.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

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(dot)albe(at)cybertec(dot)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

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Erik Wienhold 2024-03-20 14:58:57 Re: Monetary Data Types Improvement
Previous Message Greg Sabino Mullane 2024-03-19 15:04:18 Re: Discourage splitting pg_wal directory