Re: Use pg_pwrite() in pg_test_fsync - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Use pg_pwrite() in pg_test_fsync
Date
Msg-id CA+hUKGJ4VrvnD8abHx7YGkiuPwSF9UUcJQT6f-rGBuJrrKFQ1g@mail.gmail.com
Whole thread Raw
In response to Use pg_pwrite() in pg_test_fsync  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: Use pg_pwrite() in pg_test_fsync
List 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.

Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [PATCH] Disable bgworkers during servers start in pg_upgrade
Next
From: Tomas Vondra
Date:
Subject: Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits