Re: Use pread and pwrite instead of lseek + write and read

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Oskari Saarenmaa <os@ohmu.fi>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2016-08-18T19:16:16Z
Lists: pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> Well, I think you're pointing out some things that need to be figured
> out, but I hardly think that's a good enough reason to pour cold water
> on the whole approach.

If somebody feels like doing the legwork to find out if those performance
hazards are real (which I freely concede they may not be), fine.  I'm just
saying this isn't a slam-dunk commit-it-and-move-on win.

			regards, tom lane


Commits

  1. Use pg_pread() and pg_pwrite() for data files and WAL.