public inbox for [email protected]
help / color / mirror / Atom feedFrom: Sam Stearns <[email protected]>
To: Rui DeSousa <[email protected]>
Cc: Henry Ashu <[email protected]>
Cc: [email protected]
Subject: Re: Postgresql Software Location
Date: Fri, 30 Aug 2024 12:03:42 +0930
Message-ID: <CAN6TVjnm5KAeaYjXHoBG+G-xzVsbjwU5Qp2kNEsheMO5j_8WvA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CABHPps5BG3NFh4xXGjuTxs4yniXV+YNrDj8s86kOAEg7-7QG5g@mail.gmail.com>
<[email protected]>
Thanks, Rui!
On Fri, Aug 30, 2024 at 11:52 AM Rui DeSousa <[email protected]> wrote:
>
>
> On Aug 29, 2024, at 2:12 PM, Henry Ashu <[email protected]> wrote:
>
> We have installed our postgresql software in this location:
>
> [postgres@testdbapql01 data]$ pwd
> /var/lib/pgsql/16/data
> [postgres@testbapql01 data]$ df -h .
> Filesystem Size Used Avail Use% Mounted on
> /dev/mapper/rhel-root 28G 4.5G 23G 17% /
> [postgres@testdbapql01 data]$
>
> Does this look correct? We are thinking that it should not be installed on
> the root filesystem.
>
> Thank you
>
> *Henry Ashu*
>
> Database Administrator
> *o:* 503.672.5114 | *f:* 800.551.8821 | DAT.com
> [image: DAT Solutions] <https://www.dat.com/; [image: Like us on
> Facebook] <https://www.facebook.com/loadboards; [image: Follow us on
> Twitter] <https://twitter.com/loadboards; [image: Connect with us on
> LinkedIn] <https://www.linkedin.com/company/datsolutions; [image: Visit
> our YouTube Channel] <https://www.youtube.com/datloadboards; [image:
> Visit us on Instagram] <https://instagram.com/dat_solutions;
>
>
> Yes, it is better to have more mount points than not. Root should be its
> own mount point; OSs do not like when the root volume is full thus it is
> normally a very small filesystem.
>
> Disclaimer: I’ve seen servers with a single mount point /. A lot of
> devops servers are setup with a single mount point for the entire OS.
> Seems like that is the case with your system. The reason to have multiple
> filesystem is space management, mount point options, and filesystem
> corruption. I haven’t had the need to run fsck in decades until last
> month. An xfs volume was corrupted and even fsck couldn’t fix it; had to
> resort to a filesystem snapshot.
>
> I normally have three;
>
> 1. /var/log — for log files via syslog. You don’t want a run away
> application to full up the log directory and crash the server.
> 2. $PGDATA — data volume
> 3. $PGDATA/pg_wal — Normally, I’m using ZFS with different filesystem
> properties. It’s also a good idea to manage the space separately.
>
> As far as absolute mount points that’s a preference; my current gig is
> using the following with the instance names as a directory under those
> mount points.
>
> /pg_data
> /pg_wal
>
>
>
>
--
*Samuel Stearns*
Lead Database Administrator
*c:* 971 762 6879 | *o:* 503 672 5115 | DAT.com
[image: DAT]
<https://www.dat.com/?utm_medium=email&utm_source=DAT_email_signature_link;
view thread (5+ messages) latest in thread
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], [email protected]
Subject: Re: Postgresql Software Location
In-Reply-To: <CAN6TVjnm5KAeaYjXHoBG+G-xzVsbjwU5Qp2kNEsheMO5j_8WvA@mail.gmail.com>
* 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