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
    Michael Paquier authored
    When a backend exits, it gets deleted from the syncrep queue if present.
    The queue was checked without SyncRepLock taken in exclusive mode, so it
    would have been possible for a backend to remove itself after a WAL
    sender already did the job.  Fix this issue based on a suggestion from
    Fujii Masao, by first checking the queue without the lock.  Then, if the
    backend is present in the queue, take the lock and perform an additional
    lookup check before doing the element deletion.
    
    Author: Dongming Liu
    Reviewed-by: Kyotaro Horiguchi, Fujii Masao, Michael Paquier
    Discussion: https://postgr.es/m/a0806273-8bbb-43b3-bbe1-c45a58f6ae21.lingce.ldm@alibaba-inc.com
    Backpatch-through: 9.4
    7b8c2de6
    History
    Name Last commit Last update