postgresql/src/backend/parser
Peter Eisentraut 37851a8b83 Database-level collation version tracking
This adds to database objects the same version tracking that collation
objects have.  There is a new pg_database column datcollversion that
stores the version, a new function
pg_database_collation_actual_version() to get the version from the
operating system, and a new subcommand ALTER DATABASE ... REFRESH
COLLATION VERSION.

This was not originally added together with pg_collation.collversion,
since originally version tracking was only supported for ICU, and ICU
on a database-level is not currently supported.  But we now have
version tracking for glibc (since PG13), FreeBSD (since PG14), and
Windows (since PG13), so this is useful to have now.

Reviewed-by: Julien Rouhaud <rjuju123@gmail.com>
Discussion: https://www.postgresql.org/message-id/flat/f0ff3190-29a3-5b39-a179-fa32eee57db6%40enterprisedb.com
2022-02-14 08:27:26 +01:00
..
.gitignore Convert cvsignore to gitignore, and add .gitignore for build targets. 2010-09-22 12:57:04 +02:00
analyze.c Update copyright for 2022 2022-01-07 19:04:57 -05:00
check_keywords.pl Update copyright for 2022 2022-01-07 19:04:57 -05:00
gram.y Database-level collation version tracking 2022-02-14 08:27:26 +01: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 copyright for 2022 2022-01-07 19:04:57 -05:00
parse_clause.c Update copyright for 2022 2022-01-07 19:04:57 -05:00
parse_coerce.c Fix failure to validate the result of select_common_type(). 2022-01-29 11:41:18 -05:00
parse_collate.c Update copyright for 2022 2022-01-07 19:04:57 -05:00
parse_cte.c Update copyright for 2022 2022-01-07 19:04:57 -05:00
parse_enr.c Update copyright for 2022 2022-01-07 19:04:57 -05:00
parse_expr.c Fix failure to validate the result of select_common_type(). 2022-01-29 11:41:18 -05:00
parse_func.c Update copyright for 2022 2022-01-07 19:04:57 -05:00
parse_node.c Add Boolean node 2022-01-17 10:38:23 +01:00
parse_oper.c Update copyright for 2022 2022-01-07 19:04:57 -05:00
parse_param.c Update copyright for 2022 2022-01-07 19:04:57 -05:00
parse_relation.c Update copyright for 2022 2022-01-07 19:04:57 -05:00
parse_target.c Update copyright for 2022 2022-01-07 19:04:57 -05:00
parse_type.c Rename value node fields 2022-01-14 11:26:08 +01:00
parse_utilcmd.c Add UNIQUE null treatment option 2022-02-03 11:48:21 +01:00
parser.c Update copyright for 2022 2022-01-07 19:04:57 -05:00
README Move keywords.c/kwlookup.c into src/common/. 2016-03-23 20:22:08 -04:00
scan.l Update copyright for 2022 2022-01-07 19:04:57 -05:00
scansup.c Update copyright for 2022 2022-01-07 19:04:57 -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.