Re: Postgresql Database and PG_WAL locations

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Postgresql Database and PG_WAL locations
Date: 2024-09-02 10:30:32
Message-ID: 2fba534e999d3233dc4fe43aabf84622f93064eb.camel@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Thu, 2024-08-29 at 15:02 -0400, Ron Johnson wrote:
> On Thu, Aug 29, 2024 at 2:22 PM Matthew Tice <mjtice(at)gmail(dot)com> wrote:
> > > On Aug 29, 2024, at 12:18 PM, Henry Ashu <henry(dot)ashu(at)dat(dot)com> wrote:
> > >
> > > I have a database that's about 2TB in size, and I want to place the database
> > > files in a separate mount point(PGDATA) and the log files in a different mount
> > > point(PG_WAL). What's your take on this?.
> >
> >
> > Take a look at https://wiki.postgresql.org/wiki/Installation_and_Administration_Best_practices
> >
> > Essentially, yes, you will want your WAL and data stored on different devices
> > (or the very least, different partitions).
>
> Is that recommendation still valid?  After all, that was written when 15 years old
> Sun Studio 12 was still pertinent.  Times have changed since then.  Disks are much, much bigger.

I think the advice is still valid.

Today you'd have different filesystems on different logical volumes rather
than different physical disks, but it is still a good idea to separate data and WAL,
so that they cannot fill up each other's file system.

I'd actually define a third file system for the PostgreSQL log files, for
the same reason.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Ron Johnson 2024-09-02 13:15:57 Re: Postgresql Database and PG_WAL locations
Previous Message Laurenz Albe 2024-09-02 09:51:43 Re: User Privileges Issue