postgresql/src/backend/parser
Tom Lane cefa387153 Merge catalog/pg_foo_fn.h headers back into pg_foo.h headers.
Traditionally, include/catalog/pg_foo.h contains extern declarations
for functions in backend/catalog/pg_foo.c, in addition to its function
as the authoritative definition of the pg_foo catalog's rowtype.
In some cases, we'd been forced to split out those extern declarations
into separate pg_foo_fn.h headers so that the catalog definitions
could be #include'd by frontend code.  That problem is gone as of
commit 9c0a0de4c, so let's undo the splits to make things less
confusing.

Discussion: https://postgr.es/m/23690.1523031777@sss.pgh.pa.us
2018-04-08 14:35:29 -04:00
..
.gitignore Convert cvsignore to gitignore, and add .gitignore for build targets. 2010-09-22 12:57:04 +02:00
analyze.c Indexes with INCLUDE columns and their support in B-tree 2018-04-07 23:00:39 +03:00
check_keywords.pl Update copyright for 2018 2018-01-02 23:30:12 -05:00
gram.y Indexes with INCLUDE columns and their support in B-tree 2018-04-07 23:00:39 +03:00
Makefile MERGE SQL Command following SQL:2016 2018-04-03 09:28:16 +01:00
parse_agg.c Merge catalog/pg_foo_fn.h headers back into pg_foo.h headers. 2018-04-08 14:35:29 -04:00
parse_clause.c Merge catalog/pg_foo_fn.h headers back into pg_foo.h headers. 2018-04-08 14:35:29 -04:00
parse_coerce.c Merge catalog/pg_foo_fn.h headers back into pg_foo.h headers. 2018-04-08 14:35:29 -04:00
parse_collate.c MERGE SQL Command following SQL:2016 2018-04-03 09:28:16 +01:00
parse_cte.c Update copyright for 2018 2018-01-02 23:30:12 -05:00
parse_enr.c Update copyright for 2018 2018-01-02 23:30:12 -05:00
parse_expr.c MERGE SQL Command following SQL:2016 2018-04-03 09:28:16 +01:00
parse_func.c MERGE SQL Command following SQL:2016 2018-04-03 09:28:16 +01:00
parse_merge.c Improve parse representation for MERGE 2018-04-06 09:38:59 +01:00
parse_node.c Update copyright for 2018 2018-01-02 23:30:12 -05:00
parse_oper.c Update copyright for 2018 2018-01-02 23:30:12 -05:00
parse_param.c Update copyright for 2018 2018-01-02 23:30:12 -05:00
parse_relation.c Indexes with INCLUDE columns and their support in B-tree 2018-04-07 23:00:39 +03:00
parse_target.c Indexes with INCLUDE columns and their support in B-tree 2018-04-07 23:00:39 +03:00
parse_type.c Update copyright for 2018 2018-01-02 23:30:12 -05:00
parse_utilcmd.c Merge catalog/pg_foo_fn.h headers back into pg_foo.h headers. 2018-04-08 14:35:29 -04:00
parser.c Update copyright for 2018 2018-01-02 23:30:12 -05:00
README Move keywords.c/kwlookup.c into src/common/. 2016-03-23 20:22:08 -04:00
scan.l Move strtoint() to common 2018-03-13 10:21:09 -04:00
scansup.c Update copyright for 2018 2018-01-02 23:30:12 -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.