Re: Initdb-time block size specification

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: Initdb-time block size specification
Дата
Msg-id ZJ9ZMznPmBZItEot@momjian.us
обсуждение исходный текст
Ответ на Re: Initdb-time block size specification  (Tomas Vondra <tomas.vondra@enterprisedb.com>)
Ответы Re: Initdb-time block size specification
Список pgsql-hackers
On Sat, Jul  1, 2023 at 12:21:03AM +0200, Tomas Vondra wrote:
> On 6/30/23 23:53, Bruce Momjian wrote:
> > For a 4kB write, to say it is not partially written would be to require
> > the operating system to guarantee that the 4kB write is not split into
> > smaller writes which might each be atomic because smaller atomic writes
> > would not help us.
> 
> Right, that's the dance we do to protect against torn pages. But Andres
> suggested that if you have modern storage and configure it correctly,
> writing with 4kB pages would be atomic. So we wouldn't need to do this
> FPI stuff, eliminating pretty significant source of write amplification.

I agree the hardware is atomic for 4k writes, but do we know the OS
always issues 4k writes?

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: pg_upgrade instructions involving "rsync --size-only" might lead to standby corruption?
Следующее
От: Andres Freund
Дата:
Сообщение: Re: Initdb-time block size specification