diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2013-01-31 12:12:23 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2013-01-31 12:12:23 -0500 |
| commit | 9afc58396af75d59ea2eec467724faf68fe63890 (patch) | |
| tree | c1d8b77deb4ecdcfd2ddeb81603de6c5b616ca7c /src/backend/utils/adt/date.c | |
| parent | bfb8a8d3818972faf1976eccedddfaee7eb0f613 (diff) | |
Reject nonzero day fields in AT TIME ZONE INTERVAL functions.
It's not sensible for an interval that's used as a time zone value to be
larger than a day. When we changed the interval type to contain a separate
day field, check_timezone() was adjusted to reject nonzero day values, but
timetz_izone(), timestamp_izone(), and timestamptz_izone() evidently were
overlooked.
While at it, make the error messages for these three cases consistent.
Diffstat (limited to 'src/backend/utils/adt/date.c')
| -rw-r--r-- | src/backend/utils/adt/date.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/backend/utils/adt/date.c b/src/backend/utils/adt/date.c index 4e4832415a1..57391c30edf 100644 --- a/src/backend/utils/adt/date.c +++ b/src/backend/utils/adt/date.c @@ -2696,10 +2696,10 @@ timetz_izone(PG_FUNCTION_ARGS) TimeTzADT *result; int tz; - if (zone->month != 0) + if (zone->month != 0 || zone->day != 0) ereport(ERROR, (errcode(ERRCODE_INVALID_PARAMETER_VALUE), - errmsg("\"interval\" time zone \"%s\" not valid", + errmsg("interval time zone \"%s\" must not include months or days", DatumGetCString(DirectFunctionCall1(interval_out, PointerGetDatum(zone)))))); |