From: Holger Jakobs <holger@jakobs.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: WAL & ZFS
Date: Fri, 1 Apr 2022 00:47:36 +0200
Message-ID: <35c98a4b-f7a1-a896-4484-582bbaaffb5b@jakobs.com> (raw)
In-Reply-To: <43EEBE2E-4C7F-4F35-99BF-4DA8B5D3828A@crazybean.net>
References: <FC215502-166A-49DB-B3DA-D08727A34C0B@elevated-dev.com>
<43EEBE2E-4C7F-4F35-99BF-4DA8B5D3828A@crazybean.net>
The WAL is a journal itself and doesn't need another journal for safety.
Therefore, a common recommendation is using ext2 (which has no journal)
for the WAL partition.
Is this correct?
Am 31.03.22 um 23:32 schrieb Rui DeSousa:
> I would recommend a separate pg_wal filesystem with the record size to match the WAL page size; in my case 16k. I have keep the default record size at 128k for the data volume and that configuration has worked well for supporting large DSS while using 16k data blocks.
>
>> On Mar 30, 2022, at 5:32 PM, Scott Ribe <scott_ribe@elevated-dev.com> wrote:
>>
>> I've read all the info I could find re running PG on ZFS: turn off full page writes, turn on lz4, tweak recordsize so as to take advantage of compression, etc. One thing I haven't seen is whether a separate volume for WAL would benefit from a larger recordsize. Or any other tweaks???
>>
>> --
>> Scott Ribe
>> scott_ribe@elevated-dev.com
>> https://www.linkedin.com/in/scottribe/
>>
>>
>>
>>
>>
>
>
--
Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012
Attachments:
OpenPGP_signature (application/pgp-signature, 202B) download
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: pgsql-admin@postgresql.org
Cc: holger@jakobs.com, pgsql-admin@lists.postgresql.org
Subject: Re: WAL & ZFS
In-Reply-To: <35c98a4b-f7a1-a896-4484-582bbaaffb5b@jakobs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox