Re: Use pg_pwrite() in pg_test_fsync

Поиск
Список
Период
Сортировка
От Thomas Munro
Тема Re: Use pg_pwrite() in pg_test_fsync
Дата
Msg-id CA+hUKGJ4VrvnD8abHx7YGkiuPwSF9UUcJQT6f-rGBuJrrKFQ1g@mail.gmail.com
обсуждение исходный текст
Ответ на Use pg_pwrite() in pg_test_fsync  (Thomas Munro <thomas.munro@gmail.com>)
Ответы Re: Use pg_pwrite() in pg_test_fsync  (Thomas Munro <thomas.munro@gmail.com>)
Список pgsql-hackers
On Sun, Jan 10, 2021 at 9:21 AM Thomas Munro <thomas.munro@gmail.com> wrote:
> I left the fsync-after-closing and non-sync'd tests using write(),
> because they weren't using lseek().  The latter case is arguably a bit
> odd because it's not overwriting pre-allocated blocks, unlike the
> earlier tests.

On closer inspection, the weird thing about that final test is that
it's opening and closing the file every time.  That doesn't seem to
make any sense.  Perhaps it's a copy and paste error from the previous
test?  In v2 I changed it to pg_pwrite(), and moved the open and close
calls out of the loop.

Вложения

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

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: [PATCH] Disable bgworkers during servers start in pg_upgrade
Следующее
От: Tomas Vondra
Дата:
Сообщение: Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits