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

contrib

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    Fix still another bug in commit 35fcb1b3: it failed to fully initialize
    the SortSupport states it introduced to allow the executor to re-check
    ORDER BY expressions containing distance operators.  That led to a null
    pointer dereference if the sortsupport code tried to use ssup_cxt.  The
    problem only manifests in narrow cases, explaining the lack of previous
    field reports.  It requires a GiST-indexable distance operator that lacks
    SortSupport and is on a pass-by-ref data type, which among core+contrib
    seems to be only btree_gist's interval opclass; and it requires the scan
    to be done as an IndexScan not an IndexOnlyScan, which explains how
    btree_gist's regression test didn't catch it.  Per bug #14134 from
    Jihyun Yu.
    
    Peter Geoghegan
    
    Report: <20160511154904.2603.43889@wrigleys.postgresql.org>
    8a859691
    History
    Name Last commit Last update
    ..