On 2/4/18 13:10, Tom Lane wrote: > diff --git a/src/backend/utils/errcodes.txt b/src/backend/utils/errcodes.txt > index 1475bfe..9871d1e 100644 > *** a/src/backend/utils/errcodes.txt > --- b/src/backend/utils/errcodes.txt > *************** Section: Class 22 - Data Exception > *** 177,182 **** > --- 177,183 ---- > 22P06 E ERRCODE_NONSTANDARD_USE_OF_ESCAPE_CHARACTER > nonstandard_use_of_escape_character > 22010 E ERRCODE_INVALID_INDICATOR_PARAMETER_VALUE > invalid_indicator_parameter_value > 22023 E ERRCODE_INVALID_PARAMETER_VALUE > invalid_parameter_value > + 22013 E ERRCODE_INVALID_PRECEDING_FOLLOWING_SIZE > invalid_preceding_following_size > 2201B E ERRCODE_INVALID_REGULAR_EXPRESSION > invalid_regular_expression > 2201W E ERRCODE_INVALID_ROW_COUNT_IN_LIMIT_CLAUSE > invalid_row_count_in_limit_clause > 2201X E ERRCODE_INVALID_ROW_COUNT_IN_RESULT_OFFSET_CLAUSE > invalid_row_count_in_result_offset_clause
I was checking the new error codes in PostgreSQL 11 and came across this. The original name in the SQL standard is INVALID_PRECEDING_OR_FOLLOWING_SIZE_IN_WINDOW_FUNCTION which is reasonable to abbreviate, but is there a reason why we lost the "or"? -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
