aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/transam/clog.c
diff options
context:
space:
mode:
authorThomas Munro <tmunro@postgresql.org>2022-10-25 15:26:03 +1300
committerThomas Munro <tmunro@postgresql.org>2022-10-25 16:26:58 +1300
commite109e43921d21d069c03f18d7c9d8f4e5cb6a0c3 (patch)
treec43a34e6a538f8c6824ed2e2a1a66a07dd175ba2 /src/backend/access/transam/clog.c
parent4517358ee78213cd2ca18270ab4d32cd69b0b19d (diff)
downloadpostgresql-e109e43921d21d069c03f18d7c9d8f4e5cb6a0c3.tar.gz
postgresql-e109e43921d21d069c03f18d7c9d8f4e5cb6a0c3.zip
Fix unlink() for STATUS_DELETE_PENDING on Windows.
Commit f357233c assumed that it was OK to return ENOENT directly if lstat() failed that way. If we got STATUS_DELETE_PENDING while trying to unlink a file that we had already unlinked successfully once before but someone else still had open (on a kernel version that has "pending" unlinks by default), then we would no longer reach the retry loop in pgunlink(). That loop claims to be only for handling sharing violations (a different phenomenon), but the errno is the same. Restore that behavior with an explicit check, to see if it fixes the occasional 'directory not empty' failures seen in the pg_upgrade tests on CI. Further improvements are possible with proposed upgrades to modern Windows APIs that would replace this convoluted code. Reported-by: Justin Pryzby <pryzby@telsasoft.com> Reviewed-by: Michael Paquier <michael@paquier.xyz> Discussion: https://postgr.es/m/20220920013122.GA31833%40telsasoft.com Discussion: https://postgr.es/m/CA%2BhUKG%2BajSQ_8eu2AogTncOnZ5me2D-Cn66iN_-wZnRjLN%2Bicg%40mail.gmail.com
Diffstat (limited to 'src/backend/access/transam/clog.c')
0 files changed, 0 insertions, 0 deletions