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
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/9361f6f54e3ff9bab84e80d4b1e15be79b48d60e
Modified Files
--------------
doc/src/sgml/ref/create_table.sgml | 11 ++++---
src/backend/parser/parse_utilcmd.c | 48 ++++++++++++++++++++++++++++++
src/test/regress/expected/create_table.out | 12 ++++----
src/test/regress/expected/inherit.out | 4 +--
src/test/regress/expected/insert.out | 35 +++++++++++++++-------
src/test/regress/sql/create_table.sql | 6 ++--
src/test/regress/sql/inherit.sql | 4 +--
src/test/regress/sql/insert.sql | 19 +++++++-----
8 files changed, 102 insertions(+), 37 deletions(-)
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
