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
    WalSndKill was doing things exactly backwards: it should first clear
    MyWalSnd (to stop signal handlers from touching MyWalSnd->latch),
    then disown the latch, and only then mark the WalSnd struct unused by
    clearing its pid field.
    
    Also, WalRcvSigUsr1Handler and worker_spi_sighup failed to preserve
    errno, which is surely a requirement for any signal handler.
    
    Per discussion of recent buildfarm failures.  Back-patch as far
    as the relevant code exists.
    03f06ff3
    History
    Name Last commit Last update