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

postgres-lambda-diff

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    When one side of the join has a NULL, we don't want to uselessly try
    to match it against every remaining tuple of the other side.  While
    at it, rewrite the comparison machinery to avoid multiple evaluations
    of the left and right input expressions and to use a btree comparator
    where available, instead of double operator calls.  Also revise the
    state machine to eliminate redundant comparisons and hopefully make it
    more readable too.
    184e7a73
    History
    Name Last commit Last update