On 2021/08/23 15:27, Kyotaro Horiguchi wrote:
So this patch is meaningful only for v13 and later, too. Not sure what
to do for v12 and earlier but doesn't seem to be in much necessity.
Probably I failed to get your point... I was thinking that
your 0001 patch can be back-patched to v11. And also
the attached patch can be applied to v10 and v9.6. If we do this,
the log messages can be consistent between versions.
But you think that we should not change the log messages
in v12 or before, for some reasons?
I pushed your 0002 patch. Thanks!
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
diff --git a/src/backend/utils/adt/tsquery.c b/src/backend/utils/adt/tsquery.c
index fdb041971e..27b74bcbf8 100644
--- a/src/backend/utils/adt/tsquery.c
+++ b/src/backend/utils/adt/tsquery.c
@@ -163,7 +163,7 @@ parse_phrase_operator(char *buf, int16 *distance)
else if (errno == ERANGE || l < 0 || l >
MAXENTRYPOS)
ereport(ERROR,
(errcode(ERRCODE_INVALID_PARAMETER_VALUE),
- errmsg("distance in
phrase operator should not be greater than %d",
+ errmsg("distance in
phrase operator must be an integer value between zero and %d inclusive",
MAXENTRYPOS)));
else
{
