Re: Getting rid of some more lseek() calls - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Getting rid of some more lseek() calls
Date
Msg-id CA+hUKG+npCwg=qmT_t_EeVRhknVRthDfe_+SB-zHjCrwLDEADw@mail.gmail.com
Whole thread Raw
In response to Re: Getting rid of some more lseek() calls  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Getting rid of some more lseek() calls
Re: Getting rid of some more lseek() calls
List pgsql-hackers
On Thu, Feb 13, 2020 at 5:30 AM Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
> On 2020-Feb-12, Thomas Munro wrote:
> > Hmm.  Well, on Unix we have to choose between "tell me the size but
> > also change the position that I either don't care about or have to
> > undo", and "tell me the size but also tell me all this other stuff I
> > don't care about".  Since Windows apparently has GetFileSizeEx(), why
> > not use that when that's exactly what you want?  It apparently
> > understands large files.
>
> I was already thinking that it might be better to make the new function
> just "tell me the file size" without leaking the details of *how* we do
> it, before reading about this Windows call.  That reinforces it, IMO.

Ok, how about this?

Attachment

pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: Identifying user-created objects
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: Exposure related to GUC value of ssl_passphrase_command