You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
postgres/src/backend/parser
Tom Lane fa27dd40d5 Run pgindent with new pg_bsd_indent version 2.1.1. 5 years ago
..
.gitignore Convert cvsignore to gitignore, and add .gitignore for build targets. 15 years ago
Makefile Split all OBJS style lines in makefiles into one-line-per-entry style. 6 years ago
README Move keywords.c/kwlookup.c into src/common/. 10 years ago
analyze.c Run pgindent with new pg_bsd_indent version 2.1.1. 5 years ago
check_keywords.pl Update copyrights for 2020 6 years ago
gram.y Add ALTER .. NO DEPENDS ON 5 years ago
parse_agg.c Run pgindent with new pg_bsd_indent version 2.1.1. 5 years ago
parse_clause.c Run pgindent with new pg_bsd_indent version 2.1.1. 5 years ago
parse_coerce.c Put back mistakenly removed #include. 6 years ago
parse_collate.c Update copyrights for 2020 6 years ago
parse_cte.c Update copyrights for 2020 6 years ago
parse_enr.c Update copyrights for 2020 6 years ago
parse_expr.c Run pgindent with new pg_bsd_indent version 2.1.1. 5 years ago
parse_func.c Update copyrights for 2020 6 years ago
parse_node.c Go back to returning int from ereport auxiliary functions. 6 years ago
parse_oper.c Update copyrights for 2020 6 years ago
parse_param.c Update copyrights for 2020 6 years ago
parse_relation.c Reconsider the representation of join alias Vars. 6 years ago
parse_target.c Reconsider the representation of join alias Vars. 6 years ago
parse_type.c Introduce macros for typalign and typstorage constants. 6 years ago
parse_utilcmd.c Initial pgindent and pgperltidy run for v13. 5 years ago
parser.c Allow Unicode escapes in any server encoding, not only UTF-8. 6 years ago
scan.l Go back to returning int from ereport auxiliary functions. 6 years ago
scansup.c Update copyrights for 2020 6 years ago

README

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.