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

bootstrap

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    Where possible, use palloc or pg_malloc instead; otherwise, insert
    explicit NULL checks.
    
    Generally speaking, these are places where an actual OOM is quite
    unlikely, either because they're in client programs that don't
    allocate all that much, or they're very early in process startup
    so that we'd likely have had a fork() failure instead.  Hence,
    no back-patch, even though this is nominally a bug fix.
    
    Michael Paquier, with some adjustments by me
    
    Discussion: <CAB7nPqRu07Ot6iht9i9KRfYLpDaF2ZuUv5y_+72uP23ZAGysRg@mail.gmail.com>
    052cc223
    History