From 387543f7bdf0f1ca3dc06e6bb5c9ef7980cf9f44 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Mon, 11 Jun 2018 11:15:28 -0400 Subject: Make new error code name match SQL standard more closely Discussion: https://www.postgresql.org/message-id/dff3d555-bea4-ac24-29b2-29521b9d08e8%402ndquadrant.com --- src/backend/utils/adt/timestamp.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'src/backend/utils/adt/timestamp.c') diff --git a/src/backend/utils/adt/timestamp.c b/src/backend/utils/adt/timestamp.c index 265b1db7f60..1d75caebe17 100644 --- a/src/backend/utils/adt/timestamp.c +++ b/src/backend/utils/adt/timestamp.c @@ -3280,7 +3280,7 @@ in_range_timestamptz_interval(PG_FUNCTION_ARGS) if (int128_compare(interval_cmp_value(offset), int64_to_int128(0)) < 0) ereport(ERROR, - (errcode(ERRCODE_INVALID_PRECEDING_FOLLOWING_SIZE), + (errcode(ERRCODE_INVALID_PRECEDING_OR_FOLLOWING_SIZE), errmsg("invalid preceding or following size in window function"))); /* We don't currently bother to avoid overflow hazards here */ @@ -3311,7 +3311,7 @@ in_range_timestamp_interval(PG_FUNCTION_ARGS) if (int128_compare(interval_cmp_value(offset), int64_to_int128(0)) < 0) ereport(ERROR, - (errcode(ERRCODE_INVALID_PRECEDING_FOLLOWING_SIZE), + (errcode(ERRCODE_INVALID_PRECEDING_OR_FOLLOWING_SIZE), errmsg("invalid preceding or following size in window function"))); /* We don't currently bother to avoid overflow hazards here */ @@ -3342,7 +3342,7 @@ in_range_interval_interval(PG_FUNCTION_ARGS) if (int128_compare(interval_cmp_value(offset), int64_to_int128(0)) < 0) ereport(ERROR, - (errcode(ERRCODE_INVALID_PRECEDING_FOLLOWING_SIZE), + (errcode(ERRCODE_INVALID_PRECEDING_OR_FOLLOWING_SIZE), errmsg("invalid preceding or following size in window function"))); /* We don't currently bother to avoid overflow hazards here */ -- cgit v1.2.3