Re: pread() and pwrite()
Thomas Munro <thomas.munro@enterprisedb.com>
From: Thomas Munro <thomas.munro@enterprisedb.com>
To: Oskari Saarenmaa <os@ohmu.fi>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>, Tobias Oberstein <tobias.oberstein@gmail.com>
Date: 2018-07-27T02:04:05Z
Lists: pgsql-hackers
Attachments
- 0001-Use-pread-pwrite-instead-of-lseek-read-write-v3.patch (application/octet-stream) patch v3-0001
On Fri, Jul 20, 2018 at 8:14 PM, Oskari Saarenmaa <os@ohmu.fi> wrote: > On Thu, Jul 12, 2018 at 01:55:31PM +1200, Thomas Munro wrote: >> [...] I'm not even sure I'd bother adding "At" to the >> function names. If there are any extensions that want the old >> interface they will fail to compile either way. Note that the BufFile >> interface remains the same, so hopefully that covers many use cases. > > IIRC I used the "At" suffixes in my first version of the patch before > completely removing the functions which didn't take an offset argument > Now that they're gone I agree that we could just drop the "At" suffix; > "at" suffix is also used by various POSIX functions to operate in a > specific directory which may just add to confusion. Done. Rebased. -- Thomas Munro http://www.enterprisedb.com
Commits
-
Use pg_pread() and pg_pwrite() for data files and WAL.
- c24dcd0cfd94 12.0 landed
-
Provide pg_pread() and pg_pwrite() for random I/O.
- 3fd2a7932ef0 12.0 landed
-
Convert some long lists in configure.in to one-line-per-entry style.
- bfa6c5a0c974 12.0 landed