Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] lseek/read/write overhead becomes visible at scale .. - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] lseek/read/write overhead becomes visible at scale ..
Date
Msg-id CA+TgmoaTthmnFNqTD_xbGaxSg6jO8oT_VLfyUKpW71dQFC_-oQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] lseek/read/write overhead becomes visible at scale ..  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
Responses Re: [HACKERS] lseek/read/write overhead becomes visible at scale ..
List pgsql-hackers
Tree view 
On Mon, Apr 16, 2018 at 2:13 AM, Andrew Gierth
<andrew@tao11.riddles.org.uk> wrote:
> The code that detects sequential behavior can not distinguish between
> pread() and lseek+read, it looks only at the actual offset of the
> current request compared to the previous one for the same fp.
>
>  Thomas> +1 for adopting pread()/pwrite() in PG12.
>
> ditto

Likewise.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] Moving relation extension locks out of heavyweight lock manager
Next
From: Jerry Sievers
Date:
Subject: Re: Racing DEADLOCK on PostgreSQL 9.3