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
    subsequent I/O attempts fail cleanly.  I'm speculating about failure
    scenarios in which we do pq_close, then something in a proc_exit routine
    opens a file (re-using that kernel FD number), then something else
    fails and tries to write an elog message to the frontend ... message
    ends up in opened file, oops.  No known examples of this but it seems
    like a potential hole.
    2af53f37
    History
    Name Last commit Last update