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>
Subject: Re: Use pread and pwrite instead of lseek + write and read
In-reply-to: 
 <CA+TgmobQbcyHiMLA-7aBz9hcEy3PeGXLie+GzH4gyvEtEe6-Ag@mail.gmail.com>
References: <a86bd200-ebbe-d829-e3ca-0c4474b2fcb7@ohmu.fi>
 <7109.1471441241@sss.pgh.pa.us>
 <CA+TgmobEq_C2t=bqBCQnwwgfXDMbbVdfndpkfyY4vCtZFveQ2A@mail.gmail.com>
 <6352.1471461075@sss.pgh.pa.us>
 <CA+TgmobQbcyHiMLA-7aBz9hcEy3PeGXLie+GzH4gyvEtEe6-Ag@mail.gmail.com>
Comments: In-reply-to Robert Haas <robertmhaas@gmail.com>
	message dated "Thu, 18 Aug 2016 14:39:59 -0400"
Date: Thu, 18 Aug 2016 15:16:16 -0400
Message-ID: <20582.1471547776@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

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


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers