Re: Direct I/O

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, Christoph Berg <myon(at)debian(dot)org>, mikael(dot)kjellstrom(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Direct I/O
Date: 2023-05-14 23:25:23
Message-ID: CA+hUKG+z+0R2APOj8h6r+PZ=bR15uxELP0ZvU27S3Ur2-A8HMg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, May 15, 2023 at 9:09 AM Noah Misch <noah(at)leadboat(dot)com> wrote:
> This looks reasonable.

Pushed with a small change: a couple of GUC_check_errdetail strings
needed s/io_direct/debug_io_direct/. Thanks.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2023-05-14 23:26:31 Re: check_GUC_init(wal_writer_flush_after) fails with non-default block size
Previous Message Steve Chavez 2023-05-14 21:13:21 Using make_ctags leaves tags files in git