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

parse_clause.c

Blame
    • Tom Lane's avatar
      255f66ef
      Fix bug with WITH RECURSIVE immediately inside WITH RECURSIVE. 99% of the · 255f66ef
      Tom Lane authored
      code was already okay with this, but the hack that obtained the output
      column types of a recursive union in advance of doing real parse analysis
      of the recursive union forgot to handle the case where there was an inner
      WITH clause available to the non-recursive term.  Best fix seems to be to
      refactor so that we don't need the "throwaway" parse analysis step at all.
      Instead, teach the transformSetOperationStmt code to set up the CTE's output
      column information after it's processed the non-recursive term normally.
      Per report from David Fetter.
      255f66ef
      History
      Fix bug with WITH RECURSIVE immediately inside WITH RECURSIVE. 99% of the
      Tom Lane authored
      code was already okay with this, but the hack that obtained the output
      column types of a recursive union in advance of doing real parse analysis
      of the recursive union forgot to handle the case where there was an inner
      WITH clause available to the non-recursive term.  Best fix seems to be to
      refactor so that we don't need the "throwaway" parse analysis step at all.
      Instead, teach the transformSetOperationStmt code to set up the CTE's output
      column information after it's processed the non-recursive term normally.
      Per report from David Fetter.