rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
postgresql/src/backend/parser
History
Michael Paquier cdde886d36 Fix crash when using partition bound expressions 
Since 7c079d7, partition bounds are able to use generalized expression
syntax when processed, treating "minvalue" and "maxvalue" as specific
cases as they get passed down for transformation as a column references.

The checks for infinite bounds in range expressions have been lax
though, causing crashes when trying to use column reference names with
more than one field.  Here is an example causing a crash:
CREATE TABLE list_parted (a int) PARTITION BY LIST (a);
CREATE TABLE part_list_crash PARTITION OF list_parted
  FOR VALUES IN (somename.somename);

Note that the creation of the second relation should fail as partition
bounds cannot have column references in their expressions, so when
finding an expression which does not match the expected infinite bounds,
then this commit lets the generic transformation machinery check after
it.  The error message generated in this case references as well a
missing RTE, which is confusing.  This problem will be treated
separately as it impacts as well default expressions for some time, and
for now only the cases where a crash can happen are fixed.

While on it, extend the set of regression tests in place for list
partition bounds and add an extra set for range partition bounds.

Reported-by: Alexander Lakhin
Author: Michael Paquier
Reviewed-by: Amit Langote
Discussion: https://postgr.es/m/15668-0377b1981aa1a393@postgresql.org
 		2019-03-26 10:09:14 +09:00
..
.gitignore Convert cvsignore to gitignore, and add .gitignore for build targets. 2010-09-22 12:57:04 +02:00
Makefile Revert MERGE patch 2018-04-12 11:22:56 +01:00
README Move keywords.c/kwlookup.c into src/common/. 2016-03-23 20:22:08 -04:00
analyze.c Standardize some more loops that chase down parallel lists. 2019-02-28 14:25:01 -05:00
check_keywords.pl Update copyright for 2019 2019-01-02 12:44:25 -05:00
gram.y Transaction chaining 2019-03-24 11:33:02 +01:00
parse_agg.c Refactor planner's header files. 2019-01-29 15:48:51 -05:00
parse_clause.c Refactor planner's header files. 2019-01-29 15:48:51 -05:00
parse_coerce.c Update copyright for 2019 2019-01-02 12:44:25 -05:00
parse_collate.c Update copyright for 2019 2019-01-02 12:44:25 -05:00
parse_cte.c Update copyright for 2019 2019-01-02 12:44:25 -05:00
parse_enr.c Update copyright for 2019 2019-01-02 12:44:25 -05:00
parse_expr.c Renaming for new subscripting mechanism 2019-02-01 12:50:32 -03:00
parse_func.c Add unreachable "break" to satisfy -Wimplicit-fallthrough. 2019-03-23 01:32:58 -04:00
parse_node.c Renaming for new subscripting mechanism 2019-02-01 12:50:32 -03:00
parse_oper.c Update copyright for 2019 2019-01-02 12:44:25 -05:00
parse_param.c Update copyright for 2019 2019-01-02 12:44:25 -05:00
parse_relation.c Allow RECORD and RECORD[] to be specified in function coldeflists. 2019-01-30 19:25:33 -05:00
parse_target.c Renaming for new subscripting mechanism 2019-02-01 12:50:32 -03:00
parse_type.c More unconstify use 2019-02-13 11:50:16 +01:00
parse_utilcmd.c Fix crash when using partition bound expressions 2019-03-26 10:09:14 +09:00
parser.c Replace the data structure used for keyword lookup. 2019-01-06 17:02:57 -05:00
scan.l Replace the data structure used for keyword lookup. 2019-01-06 17:02:57 -05:00
scansup.c Update copyright for 2019 2019-01-02 12:44:25 -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_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.