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

src

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    Back-patch the 9.4-era commit 2636ecf7 into 9.3, as that fixes a case
    where we open a relation while not holding any lock on it.  It's
    probably mostly safe anyway, since no other session could touch the
    newly-created table; but I think CheckTableNotInUse could be fooled
    if one tried.
    
    Per testing with a patch that complains if we open a relation without
    holding any lock on it.  I don't plan to back-patch that patch, but we
    should close the holes it identifies in all supported branches.
    
    Discussion: https://postgr.es/m/2038.1538335244@sss.pgh.pa.us
    de0bea8d
    History