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

hstore_gist.c

Blame
    • Tom Lane's avatar
      cd55aa2e
      Fix two new-in-9.0 bugs in hstore. · cd55aa2e
      Tom Lane authored
      There was an incorrect Assert in hstoreValidOldFormat(), which would cause
      immediate core dumps when attempting to work with pre-9.0 hstore data,
      but of course only in an assert-enabled build.
      
      Also, ghstore_decompress() incorrectly applied DatumGetHStoreP() to a datum
      that wasn't actually an hstore, but rather a ghstore (ie, a gist signature
      bitstring).  That used to be harmless, but could now result in misbehavior
      if the hstore format conversion code happened to trigger.  In reality,
      since ghstore is not marked toastable (and doesn't need to be), this
      function is useless anyway; we can lobotomize it down to returning the
      passed-in pointer.
      
      Both bugs found by Andrew Gierth, though this isn't exactly his proposed
      patch.
      cd55aa2e
      History
      Fix two new-in-9.0 bugs in hstore.
      Tom Lane authored
      There was an incorrect Assert in hstoreValidOldFormat(), which would cause
      immediate core dumps when attempting to work with pre-9.0 hstore data,
      but of course only in an assert-enabled build.
      
      Also, ghstore_decompress() incorrectly applied DatumGetHStoreP() to a datum
      that wasn't actually an hstore, but rather a ghstore (ie, a gist signature
      bitstring).  That used to be harmless, but could now result in misbehavior
      if the hstore format conversion code happened to trigger.  In reality,
      since ghstore is not marked toastable (and doesn't need to be), this
      function is useless anyway; we can lobotomize it down to returning the
      passed-in pointer.
      
      Both bugs found by Andrew Gierth, though this isn't exactly his proposed
      patch.