Re: Postgresql Software Location

From: ji hwan song <song7357(at)gmail(dot)com>
To: Sam Stearns <sam(dot)stearns(at)dat(dot)com>
Cc: Rui DeSousa <rui(dot)desousa(at)icloud(dot)com>, Henry Ashu <henry(dot)ashu(at)dat(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Postgresql Software Location
Date: 2024-08-30 03:56:04
Message-ID: CAHTrd79A=gRaVXAzMmuTVmkjk7KtF-whPa0oHFDcOGocvV4oHg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

루트엔 설치 가급적 하지마시고 별도의 공간에 파일시스템을 만들고 해당 명칭으로 링크를 걸어주세요..

2024년 8월 30일 (금) 오전 11:34, Sam Stearns <sam(dot)stearns(at)dat(dot)com>님이 작성:

> Thanks, Rui!
>
> On Fri, Aug 30, 2024 at 11:52 AM Rui DeSousa <rui(dot)desousa(at)icloud(dot)com>
> wrote:
>
>>
>>
>> On Aug 29, 2024, at 2:12 PM, Henry Ashu <henry(dot)ashu(at)dat(dot)com> wrote:
>>
>> We have installed our postgresql software in this location:
>>
>> [postgres(at)testdbapql01 data]$ pwd
>> /var/lib/pgsql/16/data
>> [postgres(at)testbapql01 data]$ df -h .
>> Filesystem Size Used Avail Use% Mounted on
>> /dev/mapper/rhel-root 28G 4.5G 23G 17% /
>> [postgres(at)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>
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Domen Šetar 2024-08-30 08:12:56 Postgresql backup problem
Previous Message Sam Stearns 2024-08-30 02:33:42 Re: Postgresql Software Location