postgresql/src/backend/parser
Tom Lane 4d02eb017e Fix collation exposed for scalar function in FROM.
One code path in addRangeTableEntryForFunction() neglected to assign
a collation to the tupdesc entry it constructs (which is a bit odd
considering the other path did do so).  This didn't matter before commit
5815696bc, because nothing would look at the type data in this tupdesc;
but now it does.

While at it, make sure we assign the correct typmod as well.  Most
function expressions don't have a determinate typmod, but some do.

Per buildfarm, which showed failures in non-C collations, a case
I'd not thought to test for this patch :-(
2020-01-02 13:48:54 -05:00
..
.gitignore Convert cvsignore to gitignore, and add .gitignore for build targets. 2010-09-22 12:57:04 +02:00
analyze.c Make parser rely more heavily on the ParseNamespaceItem data structure. 2020-01-02 11:29:01 -05:00
check_keywords.pl Update copyrights for 2020 2020-01-01 12:21:45 -05:00
gram.y Update copyrights for 2020 2020-01-01 12:21:45 -05:00
Makefile Split all OBJS style lines in makefiles into one-line-per-entry style. 2019-11-05 14:41:07 -08:00
parse_agg.c Update copyrights for 2020 2020-01-01 12:21:45 -05:00
parse_clause.c Make parser rely more heavily on the ParseNamespaceItem data structure. 2020-01-02 11:29:01 -05:00
parse_coerce.c Make parser rely more heavily on the ParseNamespaceItem data structure. 2020-01-02 11:29:01 -05:00
parse_collate.c Update copyrights for 2020 2020-01-01 12:21:45 -05:00
parse_cte.c Update copyrights for 2020 2020-01-01 12:21:45 -05:00
parse_enr.c Update copyrights for 2020 2020-01-01 12:21:45 -05:00
parse_expr.c Make parser rely more heavily on the ParseNamespaceItem data structure. 2020-01-02 11:29:01 -05:00
parse_func.c Update copyrights for 2020 2020-01-01 12:21:45 -05:00
parse_node.c Update copyrights for 2020 2020-01-01 12:21:45 -05:00
parse_oper.c Update copyrights for 2020 2020-01-01 12:21:45 -05:00
parse_param.c Update copyrights for 2020 2020-01-01 12:21:45 -05:00
parse_relation.c Fix collation exposed for scalar function in FROM. 2020-01-02 13:48:54 -05:00
parse_target.c Make parser rely more heavily on the ParseNamespaceItem data structure. 2020-01-02 11:29:01 -05:00
parse_type.c Update copyrights for 2020 2020-01-01 12:21:45 -05:00
parse_utilcmd.c Make parser rely more heavily on the ParseNamespaceItem data structure. 2020-01-02 11:29:01 -05:00
parser.c Update copyrights for 2020 2020-01-01 12:21:45 -05:00
README Move keywords.c/kwlookup.c into src/common/. 2016-03-23 20:22:08 -04:00
scan.l Update copyrights for 2020 2020-01-01 12:21:45 -05:00
scansup.c Update copyrights for 2020 2020-01-01 12:21:45 -05:00

src/backend/parser/README

Parser
======

This directory does more than tokenize and parse SQL queries.  It also
creates Query structures for the various complex queries that are passed
to the optimizer and then executor.

parser.c	things start here
scan.l		break query into tokens
scansup.c	handle escapes in input strings
gram.y		parse the tokens and produce a "raw" parse tree
analyze.c	top level of parse analysis for optimizable queries
parse_agg.c	handle aggregates, like SUM(col1),  AVG(col2), ...
parse_clause.c	handle clauses like WHERE, ORDER BY, GROUP BY, ...
parse_coerce.c	handle coercing expressions to different data types
parse_collate.c	assign collation information in completed expressions
parse_cte.c	handle Common Table Expressions (WITH clauses)
parse_expr.c	handle expressions like col, col + 3, x = 3 or x = 4
parse_func.c	handle functions, table.column and column identifiers
parse_node.c	create nodes for various structures
parse_oper.c	handle operators in expressions
parse_param.c	handle Params (for the cases used in the core backend)
parse_relation.c support routines for tables and column handling
parse_target.c	handle the result list of the query
parse_type.c	support routines for data type handling
parse_utilcmd.c	parse analysis for utility commands (done at execution time)

See also src/common/keywords.c, which contains the table of standard
keywords and the keyword lookup function.  We separated that out because
various frontend code wants to use it too.