Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sjkZ5-003ase-Cs for pgsql-admin@arkaria.postgresql.org; Thu, 29 Aug 2024 19:12:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sjkZ3-006R5S-8P for pgsql-admin@arkaria.postgresql.org; Thu, 29 Aug 2024 19:12:13 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sjkZ2-006R4R-RW for pgsql-admin@lists.postgresql.org; Thu, 29 Aug 2024 19:12:13 +0000 Received: from mail-io1-xd33.google.com ([2607:f8b0:4864:20::d33]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sjkYz-0027v6-C0 for pgsql-admin@lists.postgresql.org; Thu, 29 Aug 2024 19:12:12 +0000 Received: by mail-io1-xd33.google.com with SMTP id ca18e2360f4ac-82a22127e97so35314139f.0 for ; Thu, 29 Aug 2024 12:12:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724958728; x=1725563528; darn=lists.postgresql.org; h=message-id:references:cc:in-reply-to:date:subject:mime-version:from :from:to:cc:subject:date:message-id:reply-to; bh=WnGBXy/oxdG/o8PXOYzWBLTlVslZt+n1WzhumXqE+qc=; b=ieq/UHkT7LAVx0+FF3apb77e77XmokWZ1sjjtqGtjlCBdqVhCHcP6t/ICeC6S4xtGy shHXwBvacHH93/F2VudMyxq0LpCD5/yf8Sn6NVL2AHbm91GX9BqXU1wluVGAoEvgeAT6 Kc96fvq3bBY0kZS6hcY9VadzQB7OfdPewmB8Rcgm3e2syPQ1Vjdo2qtgeD5M9P6tcTU2 7sPrFv1IGss33uTy/aBr5UJAabESXldLqtMZORe9dazTuYHDRhJCcO2gT22VC9Ky2Bd6 AWzRwKgzM1B0uGCBPjIV3lad8t2dsYWYG78Vu9Zf3qcKs+l8V3Fa38LVv07BOaWfLmsX fAhA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724958728; x=1725563528; h=message-id:references:cc:in-reply-to:date:subject:mime-version:from :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=WnGBXy/oxdG/o8PXOYzWBLTlVslZt+n1WzhumXqE+qc=; b=f3SJq0V4ygbK3dsXZAvv1TsYpmLMe2mINbnLyt60GKLulUmkWrH0f2RpQZPyKSQuWq qwWAEVa8Xz+Kd+NN0JAHqGfMrpAoeO37DmR5rjHDkp9sIJFSpre07TJtS1cVrW1MKoYb WCNsOmTKDbstSCdWbtpWcp2e7znaK1c01Jd978x+2edPWNSWdbBuNiCRLTmTagj3U+Q9 d8cZB0cVb4n9HZyEuM/VwxzQ4UkNloR2aF3bv0VJop9JtokPCXjxqoC3Uzl6mPgEYJKI dx6O2NCekN2oLerbJdNJpEIb7eRi4m7Yy3U9NIpvChK4I/v1XxAlsXIsx5pkWK5OeQho gB9g== X-Gm-Message-State: AOJu0Yw/jqPTtARIzrW1Xfp14MUqtatG6q2j0PLVWypuTwwVIgzsYBt6 jQ9Ikxdfa74nWmjdYRbjf3oFUbh0TAvdj6I/TT97seR41nLg/T7/LSsJLg6L X-Google-Smtp-Source: AGHT+IEsI/btFgshP3NsaAonI64OOhgyVQ8yC/+ZO396874gNo7OFvZGezsOsUJP3sej725ZZQAAvA== X-Received: by 2002:a05:6602:15d4:b0:82a:217c:eb94 with SMTP id ca18e2360f4ac-82a217ceccbmr203772639f.13.1724958728191; Thu, 29 Aug 2024 12:12:08 -0700 (PDT) Received: from smtpclient.apple (97-117-96-201.slkc.qwest.net. [97.117.96.201]) by smtp.gmail.com with ESMTPSA id 8926c6da1cb9f-4ced2eaac50sm358426173.137.2024.08.29.12.12.07 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 29 Aug 2024 12:12:07 -0700 (PDT) From: Matthew Tice Content-Type: multipart/alternative; boundary="Apple-Mail=_5E73866C-C0D1-4703-A88C-4BC6EE61717B" Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51\)) Subject: Re: Postgresql Database and PG_WAL locations Date: Thu, 29 Aug 2024 13:11:57 -0600 In-Reply-To: Cc: Pgsql-admin References: <5BDE97CE-242C-479A-BDC7-CF263BBD554B@gmail.com> Message-Id: X-Mailer: Apple Mail (2.3776.700.51) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --Apple-Mail=_5E73866C-C0D1-4703-A88C-4BC6EE61717B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Aug 29, 2024, at 1:02=E2=80=AFPM, Ron Johnson = wrote: >=20 > On Thu, Aug 29, 2024 at 2:22=E2=80=AFPM Matthew Tice > wrote: >>> On Aug 29, 2024, at 12:18=E2=80=AFPM, Henry Ashu > wrote: >>>=20 >>> 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?. >>>=20 >>=20 >> Take a look at = https://wiki.postgresql.org/wiki/Installation_and_Administration_Best_prac= tices >>=20 >> Essentially, yes, you will want your WAL and data stored on different = devices (or the very least, different partitions). >=20 >=20 > 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. Good point. I didn=E2=80=99t even notice that disclaimer at the top = "Seek knowledge elsewhere, as the material in here predates Postgres 9 = it seems.=E2=80=9D=E2=80=A6 But regarding the wal/data separation, I still think it=E2=80=99s = relevant (isolating the IO between data files and wal). But I guess = like anything else it depends on your workload (and, in this case, your = storage subsystem capabilities). >=20 > -- > Death to America, and butter sauce. > Iraq lobster! --Apple-Mail=_5E73866C-C0D1-4703-A88C-4BC6EE61717B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8


On Aug 29, 2024, at 1:02=E2=80=AFPM, Ron Johnson = <ronljohnsonjr@gmail.com> wrote:

On Thu, Aug 29, 2024 at 2:22=E2=80=AFPM Matthew Tice <mjtice@gmail.com> = wrote:
On Aug 29, 2024, at 12:18=E2=80=AFPM, Henry Ashu = <henry.ashu@dat.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?.



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.

Good point. =  I didn=E2=80=99t even notice that disclaimer at the top "Seek knowledge = elsewhere, as the material in here predates Postgres 9 it = seems.=E2=80=9D=E2=80=A6

But regarding the wal/data separation, = I still think it=E2=80=99s relevant (isolating the IO between data files = and wal).  But I guess like anything else it depends on your = workload (and, in this case, your storage subsystem = capabilities).


-- =
Death to America, and butter sauce.
Iraq = lobster!

= --Apple-Mail=_5E73866C-C0D1-4703-A88C-4BC6EE61717B--