Re: PostgreSQL 18 Beta 1 release announcement draft - Mailing list pgsql-hackers

From Andres Freund
Subject Re: PostgreSQL 18 Beta 1 release announcement draft
Date
Msg-id x7e3cjwjmf4f2iwhesaqygiovngsataukuygaoil73gfjt32n6@2wm4ychgolet
Whole thread Raw
In response to Re: PostgreSQL 18 Beta 1 release announcement draft  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Hi,

On 2025-05-06 16:53:46 -0400, Bruce Momjian wrote:
> On Tue, May  6, 2025 at 11:55:53AM -0400, Andres Freund wrote:
> > On 2025-05-05 15:07:01 -0400, Jonathan S. Katz wrote:
> > > ### Performance
> > >
> > > PostgreSQL 18 introduces an asynchronous I/O (AIO) subsystem using
> > > `io_uring` on Linux, which, when combined with direct I/O (DIO), lets
> > > PostgreSQL directly interface with storage interfaces. This new subsystem
> > > gives PostgreSQL the opportunity to maximize its usage of hardware transfer
> > > capacity, and this initial release supporting file system reads such as
> > > sequential scans, bitmap heap scans, and vacuums, with tests showing up to a
> > > 2-3x performance improvements.
> > 
> > This isn't quite right:
> > 
> > - AIO is usable on all platforms, it *optionally* can use io_uring on linux -
> >   the default is to use AIO using worker processes
> 
> Actually, is AIO using worker processes new behavior or just a new
> implementation of our old behavior?  I might need to point that out in
> the release notes.

New.

- Andres



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: regdatabase
Next
From: Cédric Villemain
Date:
Subject: Re: Add time spent in posix_fadvise() in I/O read time ?