From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Mladen Gogala <gogala.mladen@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: WAL & ZFS
Date: Thu, 31 Mar 2022 17:13:29 -0600
Message-ID: <26C01C4E-9D90-4E18-9976-6A1457428931@elevated-dev.com> (raw)
In-Reply-To: <1dd2bcec-c145-b65b-21b8-0e391b05e8e4@gmail.com>
References: <FC215502-166A-49DB-B3DA-D08727A34C0B@elevated-dev.com>
<43EEBE2E-4C7F-4F35-99BF-4DA8B5D3828A@crazybean.net>
<35c98a4b-f7a1-a896-4484-582bbaaffb5b@jakobs.com>
<1dd2bcec-c145-b65b-21b8-0e391b05e8e4@gmail.com>
> On Mar 31, 2022, at 5:09 PM, Mladen Gogala <gogala.mladen@gmail.com> wrote:
>
> Journallng file systems journal file operations like open, close, create, extend, rename or delete, not file block operations. File blocks are not protected by file system journalling, just the inodes. The file system journal prevents you from losing files in case of sudden machine crash, like when the machine loses power. It has nothing to do with the block change journaling, which is the role of WAL files.
LOL, I *knew* that about journaling file systems, thanks for reminding me!
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: scott_ribe@elevated-dev.com, gogala.mladen@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: WAL & ZFS
In-Reply-To: <26C01C4E-9D90-4E18-9976-6A1457428931@elevated-dev.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