Horton

After a MINVALUE/MAXVALUE bound, allow only more of the same.

Robert Haas <rhaas@postgresql.org>

View on postgr.es
Commit: 9361f6f54e3ff9bab84e80d4b1e15be79b48d60e
Author: Robert Haas <rhaas@postgresql.org>
Date: 2017-09-16T01:15:55Z
Releases: 11.0 
After a MINVALUE/MAXVALUE bound, allow only more of the same.

In the old syntax, which used UNBOUNDED, we had a similar restriction,
but commit d363d42bb9a4399a0207bd3b371c966e22e06bd3, which changed the
syntax, eliminated it.  Put it back.

Patch by me, reviewed by Dean Rasheed.

Discussion: http://postgr.es/m/CA+Tgmobs+pLPC27tS3gOpEAxAffHrq5w509cvkwTf9pF6cWYbg@mail.gmail.com

Files

PathChange+/−
doc/src/sgml/ref/create_table.sgml modified +5 −6
src/backend/parser/parse_utilcmd.c modified +48 −0
src/test/regress/expected/create_table.out modified +6 −6
src/test/regress/expected/inherit.out modified +2 −2
src/test/regress/expected/insert.out modified +24 −11
src/test/regress/sql/create_table.sql modified +3 −3
src/test/regress/sql/inherit.sql modified +2 −2
src/test/regress/sql/insert.sql modified +12 −7

Documentation touched

Discussion