diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2017-09-11 22:02:58 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2017-09-11 22:02:58 -0400 |
| commit | e183530550dc1b73d24fb5ae7d84e85286e88ffb (patch) | |
| tree | 012da06cc5da236e9d8acc314f787cbf1cf28834 /src/backend/executor/nodeBitmapIndexscan.c | |
| parent | 57e1c007939447ecf8c2d2aa2f507124613324ad (diff) | |
| download | postgresql-e183530550dc1b73d24fb5ae7d84e85286e88ffb.tar.gz postgresql-e183530550dc1b73d24fb5ae7d84e85286e88ffb.zip | |
Fix RecursiveCopy.pm to cope with disappearing files.
When copying from an active database tree, it's possible for files to be
deleted after we see them in a readdir() scan but before we can open them.
(Once we've got a file open, we don't expect any further errors from it
getting unlinked, though.) Tweak RecursiveCopy so it can cope with this
case, so as to avoid irreproducible test failures.
Back-patch to 9.6 where this code was added. In v10 and HEAD, also
remove unused "use RecursiveCopy" in one recovery test script.
Michael Paquier and Tom Lane
Discussion: https://postgr.es/m/24621.1504924323@sss.pgh.pa.us
Diffstat (limited to 'src/backend/executor/nodeBitmapIndexscan.c')
0 files changed, 0 insertions, 0 deletions