Commit 8ec8fe0f authored by Peter Eisentraut's avatar Peter Eisentraut

Message style fix

Don't quote type name placeholders.
parent c82d59d6
...@@ -4755,7 +4755,7 @@ satisfies_hash_partition(PG_FUNCTION_ARGS) ...@@ -4755,7 +4755,7 @@ satisfies_hash_partition(PG_FUNCTION_ARGS)
if (argtype != key->parttypid[j] && !IsBinaryCoercible(argtype, key->parttypid[j])) if (argtype != key->parttypid[j] && !IsBinaryCoercible(argtype, key->parttypid[j]))
ereport(ERROR, ereport(ERROR,
(errcode(ERRCODE_INVALID_PARAMETER_VALUE), (errcode(ERRCODE_INVALID_PARAMETER_VALUE),
errmsg("column %d of the partition key has type \"%s\", but supplied value is of type \"%s\"", errmsg("column %d of the partition key has type %s, but supplied value is of type %s",
j + 1, format_type_be(key->parttypid[j]), format_type_be(argtype)))); j + 1, format_type_be(key->parttypid[j]), format_type_be(argtype))));
fmgr_info_copy(&my_extra->partsupfunc[j], fmgr_info_copy(&my_extra->partsupfunc[j],
......
...@@ -48,7 +48,7 @@ SELECT satisfies_hash_partition('mchash'::regclass, 3, 1, NULL::int); ...@@ -48,7 +48,7 @@ SELECT satisfies_hash_partition('mchash'::regclass, 3, 1, NULL::int);
ERROR: number of partitioning columns (2) does not match number of partition keys provided (1) ERROR: number of partitioning columns (2) does not match number of partition keys provided (1)
-- wrong argument type -- wrong argument type
SELECT satisfies_hash_partition('mchash'::regclass, 2, 1, NULL::int, NULL::int); SELECT satisfies_hash_partition('mchash'::regclass, 2, 1, NULL::int, NULL::int);
ERROR: column 2 of the partition key has type "text", but supplied value is of type "integer" ERROR: column 2 of the partition key has type text, but supplied value is of type integer
-- ok, should be false -- ok, should be false
SELECT satisfies_hash_partition('mchash'::regclass, 4, 0, 0, ''::text); SELECT satisfies_hash_partition('mchash'::regclass, 4, 0, 0, ''::text);
satisfies_hash_partition satisfies_hash_partition
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment