postgresql/src/backend/parser
Peter Eisentraut 46a0cd4cef Add temporal PRIMARY KEY and UNIQUE constraints
Add WITHOUT OVERLAPS clause to PRIMARY KEY and UNIQUE constraints.
These are backed by GiST indexes instead of B-tree indexes, since they
are essentially exclusion constraints with = for the scalar parts of
the key and && for the temporal part.

Author: Paul A. Jungwirth <pj@illuminatedcomputing.com>
Reviewed-by: Peter Eisentraut <peter@eisentraut.org>
Reviewed-by: jian he <jian.universality@gmail.com>
Discussion: https://www.postgresql.org/message-id/flat/CA+renyUApHgSZF9-nd-a0+OPGharLQLO=mDHcY4_qQ0+noCUVg@mail.gmail.com
2024-01-24 16:34:37 +01:00
..
.gitignore Convert cvsignore to gitignore, and add .gitignore for build targets. 2010-09-22 12:57:04 +02:00
Makefile Remove distprep 2023-11-06 15:18:04 +01:00
README Remove outdated reference to a removed file 2023-06-15 22:35:42 +09:00
analyze.c Add hint about not qualifying UPDATE...SET target with relation name. 2024-01-20 17:54:14 -05:00
check_keywords.pl Update copyright for 2024 2024-01-03 20:49:05 -05:00
gram.y Add temporal PRIMARY KEY and UNIQUE constraints 2024-01-24 16:34:37 +01:00
gramparse.h Update copyright for 2024 2024-01-03 20:49:05 -05:00
meson.build Update copyright for 2024 2024-01-03 20:49:05 -05:00
parse_agg.c Update copyright for 2024 2024-01-03 20:49:05 -05:00
parse_clause.c Update copyright for 2024 2024-01-03 20:49:05 -05:00
parse_coerce.c Update copyright for 2024 2024-01-03 20:49:05 -05:00
parse_collate.c Update copyright for 2024 2024-01-03 20:49:05 -05:00
parse_cte.c Update copyright for 2024 2024-01-03 20:49:05 -05:00
parse_enr.c Update copyright for 2024 2024-01-03 20:49:05 -05:00
parse_expr.c Update copyright for 2024 2024-01-03 20:49:05 -05:00
parse_func.c Update copyright for 2024 2024-01-03 20:49:05 -05:00
parse_merge.c Update copyright for 2024 2024-01-03 20:49:05 -05:00
parse_node.c Update copyright for 2024 2024-01-03 20:49:05 -05:00
parse_oper.c Update copyright for 2024 2024-01-03 20:49:05 -05:00
parse_param.c Update copyright for 2024 2024-01-03 20:49:05 -05:00
parse_relation.c Update copyright for 2024 2024-01-03 20:49:05 -05:00
parse_target.c Update copyright for 2024 2024-01-03 20:49:05 -05:00
parse_type.c Update copyright for 2024 2024-01-03 20:49:05 -05:00
parse_utilcmd.c Add temporal PRIMARY KEY and UNIQUE constraints 2024-01-24 16:34:37 +01:00
parser.c Update copyright for 2024 2024-01-03 20:49:05 -05:00
scan.l Update copyright for 2024 2024-01-03 20:49:05 -05:00
scansup.c Update copyright for 2024 2024-01-03 20:49:05 -05:00

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_enr.c	handle ephemeral named rels (trigger transition tables, ...)
parse_func.c	handle functions, table.column and column identifiers
parse_merge.c	handle MERGE
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.