| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Pinned files at Windows |
| Date: | 2019-06-04 00:18:21 |
| Message-ID: | 20190604001821.GB1529@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 03, 2019 at 11:37:30PM +0300, Konstantin Knizhnik wrote:
> but without success because ERROR_DELETE_PENDING is never returned by Win32.
> And moreover, stat() doesn't ever return error in this case.
Could it be possible to find a reliable way to detect that?
Cloberring errno with an incorrect value is not something we can rely
on, and I am ready to buy that GetFileAttributesEx() can also return
EACCES for some legit cases, like a file it has no access to. What
if for example something is done on a file between the stat() call and
the GetFileAttributesEx() call in pgwin32_safestat() so as EACCES is
a legit error?
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashwin Agrawal | 2019-06-04 00:24:15 | Re: Comment typo in tableam.h |
| Previous Message | Ashwin Agrawal | 2019-06-03 23:53:48 | Re: Confusing error message for REINDEX TABLE CONCURRENTLY |