Skip to content
Snippets Groups Projects
  • Tom Lane's avatar
    3eb1c822
    Fix planner and rewriter to follow SQL semantics for tables that are · 3eb1c822
    Tom Lane authored
    mentioned in FROM but not elsewhere in the query: such tables should be
    joined over anyway.  Aside from being more standards-compliant, this allows
    removal of some very ugly hacks for COUNT(*) processing.  Also, allow
    HAVING clause without aggregate functions, since SQL does.  Clean up
    CREATE RULE statement-list syntax the same way Bruce just fixed the
    main stmtmulti production.
    CAUTION: addition of a field to RangeTblEntry nodes breaks stored rules;
    you will have to initdb if you have any rules.
    3eb1c822
    History
    Fix planner and rewriter to follow SQL semantics for tables that are
    Tom Lane authored
    mentioned in FROM but not elsewhere in the query: such tables should be
    joined over anyway.  Aside from being more standards-compliant, this allows
    removal of some very ugly hacks for COUNT(*) processing.  Also, allow
    HAVING clause without aggregate functions, since SQL does.  Clean up
    CREATE RULE statement-list syntax the same way Bruce just fixed the
    main stmtmulti production.
    CAUTION: addition of a field to RangeTblEntry nodes breaks stored rules;
    you will have to initdb if you have any rules.