Skip to content
Snippets Groups Projects
Select Git revision
  • benchmark-tools
  • postgres-lambda
  • master default
  • REL9_4_25
  • REL9_5_20
  • REL9_6_16
  • REL_10_11
  • REL_11_6
  • REL_12_1
  • REL_12_0
  • REL_12_RC1
  • REL_12_BETA4
  • REL9_4_24
  • REL9_5_19
  • REL9_6_15
  • REL_10_10
  • REL_11_5
  • REL_12_BETA3
  • REL9_4_23
  • REL9_5_18
  • REL9_6_14
  • REL_10_9
  • REL_11_4
23 results

postgres-lambda-diff

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    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
    bd18960c
    History
    Name Last commit Last update