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
    SELECT DISTINCT ON (expr [, expr ...]) targetlist ...
    and there is a check to make sure that the user didn't specify an ORDER BY
    that's incompatible with the DISTINCT operation.
    Reimplement nodeUnique and nodeGroup to use the proper datatype-specific
    equality function for each column being compared --- they used to do
    bitwise comparisons or convert the data to text strings and strcmp().
    (To add insult to injury, they'd look up the conversion functions once
    for each tuple...)  Parse/plan representation of DISTINCT is now a list
    of SortClause nodes.
    initdb forced by querytree change...
    dd979f66
    History
    Name Last commit Last update