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

executor

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    These two routines will now ALWAYS elog() on failure, whether you ask for
    a lock or not.  If you really want to get a NULL return on failure, call
    the new routines heap_open_nofail()/heap_openr_nofail().  By my count there
    are only about three places that actually want that behavior.  There were
    rather more than three places that were missing the check they needed to
    make under the old convention :-(.
    61aca818
    History