Re: Should we nonblocking open FIFO files in COPY? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Should we nonblocking open FIFO files in COPY?
Date
Msg-id CA+TgmoaS9-QxSRKrrFUMBkAbFxYsUT+BJT5Ea4qtQi50u4VHCg@mail.gmail.com
Whole thread Raw
In response to Re: Should we nonblocking open FIFO files in COPY?  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Should we nonblocking open FIFO files in COPY?
List pgsql-hackers
On Tue, Dec 26, 2017 at 7:51 PM, Michael Paquier
<michael.paquier@gmail.com> wrote:
>> > Hmm.  What about the case where we try to open a plain file that's on
>> > an inaccessible filesystem, e.g. due to a disk failure?  Allowing
>> > cancel to work just for FIFOs would be OK, I guess, but allowing it
>> > for other open() calls that hang would be better.  I'm not sure if we
>> > can make it work that way, but it would be nice if we could.
>>
>> That is doable, just stat() and check before open().
>
> I think TOCTOU when I read such things.. The data folder is a trusted
> environment but any patches doing things like that ought to be careful.

Yeah.  I was more wondering whether an ostensibly non-blocking open()
would nevertheless block on an inaccessible file.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: [HACKERS] Transactions involving multiple postgres foreign servers
Next
From: Robert Haas
Date:
Subject: Re: Observations in Parallel Append