From: | Rui DeSousa <rui(at)crazybean(dot)net> |
---|---|
To: | Holger Jakobs <holger(at)jakobs(dot)com> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: WAL & ZFS |
Date: | 2022-04-01 17:39:52 |
Message-ID: | B8A263D9-7741-416C-96FF-BD3B19925CA5@crazybean.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
!=. Journal filesystem is only going to journal the metadata. ZFS will guarantee the your WAL page is either written or not. That is not the case with a journaled filesystem.
I wouldn’t recommend doing that; if you are using ZFS then use it for both data and WALs.
> On Mar 31, 2022, at 6:47 PM, Holger Jakobs <holger(at)jakobs(dot)com> wrote:
>
> 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(at)elevated-dev(dot)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(at)elevated-dev(dot)com
>>> https://www.linkedin.com/in/scottribe/
>>>
>>>
>>>
>>>
>>>
>>
>>
> --
> Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012
>
From | Date | Subject | |
---|---|---|---|
Next Message | Rui DeSousa | 2022-04-01 17:49:46 | Re: WAL & ZFS |
Previous Message | Scott Ribe | 2022-04-01 02:54:11 | Re: WAL & ZFS |