diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2003-05-04 00:03:55 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2003-05-04 00:03:55 +0000 |
| commit | ac5fdea6877acd8d646feac8fae78675ad5e294d (patch) | |
| tree | 517451e2385bcbfa0047e19e374fd3e0e9c802df /src/backend/commands/dbcommands.c | |
| parent | 228697179adac8da31e0a832e730d0927cf6d0c1 (diff) | |
| download | postgresql-ac5fdea6877acd8d646feac8fae78675ad5e294d.tar.gz postgresql-ac5fdea6877acd8d646feac8fae78675ad5e294d.zip | |
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.
Diffstat (limited to 'src/backend/commands/dbcommands.c')
0 files changed, 0 insertions, 0 deletions