| From: | tgl(at)postgresql(dot)org (Tom Lane) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql-server/ oc/src/sgml/ref/create_table.sgm ... |
| Date: | 2003-05-04 00:03:55 |
| Message-ID: | 20030504000355.9CA22476414@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
CVSROOT: /cvsroot
Module name: pgsql-server
Changes by: tgl(at)postgresql(dot)org 03/05/03 20:03:55
Modified files:
doc/src/sgml/ref: create_table.sgml create_table_as.sgml
src/backend/parser: gram.y
Log message:
When a TIMESTAMP, TIME, or INTERVAL precision is specified larger than our
implementation limits, do not issue an ERROR; instead issue a NOTICE and use
the max supported value. Per pgsql-general discussion of 28-Apr, this is
needed to allow easy porting from pre-7.3 releases where the limits were
higher.
Unrelated change in same area: accept GLOBAL TEMP/TEMPORARY as a synonym
for TEMPORARY, as per pgsql-hackers discussion of 15-Apr. We previously
rejected it, but that was based on a misreading of the spec --- SQL92's
GLOBAL temp tables are really closer to what we have than their LOCAL ones.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-05-04 00:04:10 | pgsql-server/src/backend/parser Tag: REL7_3_ST ... |
| Previous Message | Tom Lane | 2003-05-03 22:19:18 | pgsql-server/src/bin/pg_dump Tag: REL7_3_STABL ... |