Re: pread() and pwrite()

From: Jesper Pedersen <jesper(dot)pedersen(at)redhat(dot)com>
To: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Oskari Saarenmaa <os(at)ohmu(dot)fi>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Tobias Oberstein <tobias(dot)oberstein(at)gmail(dot)com>
Subject: Re: pread() and pwrite()
Date: 2018-11-05 13:44:34
Message-ID: 13bf4246-061f-6187-e881-547a82379f70@redhat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Thomas,

On 11/5/18 7:08 AM, Thomas Munro wrote:
> On Sun, Nov 4, 2018 at 12:03 AM Thomas Munro
> <thomas(dot)munro(at)enterprisedb(dot)com> wrote:
>> On Sat, Nov 3, 2018 at 2:07 AM Jesper Pedersen
>> <jesper(dot)pedersen(at)redhat(dot)com> wrote:
>>> This still applies, and passes make check-world.
>>>
>>> I wonder what the commit policy is on this, if the Windows part isn't
>>> included. I read Heikki's comment [1] as it would be ok to commit
>>> benefiting all platforms that has pread/pwrite.
>>
>> Here's a patch to add Windows support by supplying
>> src/backend/port/win32/pread.c. Thoughts?
>
> If we do that, I suppose we might as well supply implementations for
> HP-UX 10.20 as well, and then we can get rid of the conditional macro
> stuff at various call sites and use pread() and pwrite() freely.
> Here's a version that does it that way. One question is whether the
> caveat mentioned in patch 0001 is acceptable.
>

Passed check-world, but I can't verify the 0001 patch. Reading the the
API it looks ok to me.

I guess the caveat in 0001 is ok, as it is a side-effect of the
underlying API.

Best regards,
Jesper

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2018-11-05 14:08:33 Re: Reduce maintenance burden of alternative output files with \if \quit
Previous Message Tatsuo Ishii 2018-11-05 12:48:09 Re: Code of Conduct plan,Re: Code of Conduct plan,Re: Code of Conduct plan,Re: Code of Conduct plan