Re: Large block sizes support in Linux

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Pankaj Raghav <kernel(at)pankajraghav(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, p(dot)raghav(at)samsung(dot)com, mcgrof(at)kernel(dot)org, gost(dot)dev(at)samsung(dot)com
Subject: Re: Large block sizes support in Linux
Date: 2024-03-25 20:31:50
Message-ID: CA+hUKGKkk0tLj+1KEuJM_x7ZogGDR8zHMJatWqC0P8ZJvq0VVA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 26, 2024 at 3:34 AM Pankaj Raghav <kernel(at)pankajraghav(dot)com> wrote:
> One question: Does ZFS do something like FUA request to force the device
> to clear the cache before it can update the node to point to the new page?
>
> If it doesn't do it, there is no guarantee from device to update the data
> atomically unless it has bigger atomic guarantees?

It flushes the whole disk write cache (unless you turn that off).
AFAIK it can't use use FUA instead yet (it knows some things about it,
there are mentions under the Linux-specific parts of the tree but that
may be more to do with understanding and implementing it when
exporting a virtual block device, or something like that (?), but I
don't believe it knows how to use it for its own underlying log or
ordering). FUA would clearly be better, no waiting for random extra
data to be flushed.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2024-03-25 20:33:16 Re: Why is parula failing?
Previous Message Bharath Rupireddy 2024-03-25 20:20:42 Re: pgsql: Track last_inactive_time in pg_replication_slots.