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

nodeMergejoin.c

Blame
    • Tom Lane's avatar
      90f4c2d9
      Add support for doing FULL JOIN ON FALSE. While this is really a rather · 90f4c2d9
      Tom Lane authored
      peculiar variant of UNION ALL, and so wouldn't likely get written directly
      as-is, it's possible for it to arise as a result of simplification of
      less-obviously-silly queries.  In particular, now that we can do flattening
      of subqueries that have constant outputs and are underneath an outer join,
      it's possible for the case to result from simplification of queries of the
      type exhibited in bug #5263.  Back-patch to 8.4 to avoid a functionality
      regression for this type of query.
      90f4c2d9
      History
      Add support for doing FULL JOIN ON FALSE. While this is really a rather
      Tom Lane authored
      peculiar variant of UNION ALL, and so wouldn't likely get written directly
      as-is, it's possible for it to arise as a result of simplification of
      less-obviously-silly queries.  In particular, now that we can do flattening
      of subqueries that have constant outputs and are underneath an outer join,
      it's possible for the case to result from simplification of queries of the
      type exhibited in bug #5263.  Back-patch to 8.4 to avoid a functionality
      regression for this type of query.