database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-01 14:21:49 +03:00
Code

Disallow creating binary-coercible casts involving range types.

Browse Source 
For a long time we have forbidden binary-coercible casts to or from
composite and array types, because such a cast cannot work correctly:
the type OID embedded in the value would need to change, but it won't
in a binary coercion.  That reasoning applies equally to range types,
but we overlooked installing a similar restriction here when we
invented range types.  Do so now.

Given the lack of field complaints, we won't change this in stable
branches, but it seems not too late for v17.

Per discussion of a problem noted by Peter Eisentraut.

Discussion: https://postgr.es/m/076968e1-0852-40a9-bc0b-117cd3f0e43c@eisentraut.org
This commit is contained in:
Tom Lane 2024-08-21 12:00:03 -04:00
parent 0c7ec3b3a0
commit 2366ab246a
1 changed files with 24 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

35
src/backend/commands/functioncmds.c
View File

@ -1689,13 +1689,18 @@ CreateCast(CreateCastStmt *stmt)
errmsg("source and target data types are not physically compatible"))); errmsg("source and target data types are not physically compatible")));
/* /*
* We know that composite, enum and array types are never binary- * We know that composite, array, range and enum types are never
* compatible with each other. They all have OIDs embedded in them. * binary-compatible with each other. They all have OIDs embedded in
* them.
* *
* Theoretically you could build a user-defined base type that is * Theoretically you could build a user-defined base type that is
* binary-compatible with a composite, enum, or array type. But we * binary-compatible with such a type. But we disallow it anyway, as
* disallow that too, as in practice such a cast is surely a mistake. * in practice such a cast is surely a mistake. You can always work
* You can always work around that by writing a cast function. * around that by writing a cast function.
*
* NOTE: if we ever have a kind of container type that doesn't need to
* be rejected for this reason, we'd likely need to recursively apply
* all of these same checks to the contained type(s).
*/ */
if (sourcetyptype == TYPTYPE_COMPOSITE || if (sourcetyptype == TYPTYPE_COMPOSITE ||
targettyptype == TYPTYPE_COMPOSITE) targettyptype == TYPTYPE_COMPOSITE)
@ -1703,18 +1708,26 @@ CreateCast(CreateCastStmt *stmt)
(errcode(ERRCODE_INVALID_OBJECT_DEFINITION), (errcode(ERRCODE_INVALID_OBJECT_DEFINITION),
errmsg("composite data types are not binary-compatible"))); errmsg("composite data types are not binary-compatible")));
if (sourcetyptype == TYPTYPE_ENUM ||
targettyptype == TYPTYPE_ENUM)
ereport(ERROR,
(errcode(ERRCODE_INVALID_OBJECT_DEFINITION),
errmsg("enum data types are not binary-compatible")));
if (OidIsValid(get_element_type(sourcetypeid)) || if (OidIsValid(get_element_type(sourcetypeid)) ||
OidIsValid(get_element_type(targettypeid))) OidIsValid(get_element_type(targettypeid)))
ereport(ERROR, ereport(ERROR,
(errcode(ERRCODE_INVALID_OBJECT_DEFINITION), (errcode(ERRCODE_INVALID_OBJECT_DEFINITION),
errmsg("array data types are not binary-compatible"))); errmsg("array data types are not binary-compatible")));
if (sourcetyptype == TYPTYPE_RANGE ||
targettyptype == TYPTYPE_RANGE ||
sourcetyptype == TYPTYPE_MULTIRANGE ||
targettyptype == TYPTYPE_MULTIRANGE)
ereport(ERROR,
(errcode(ERRCODE_INVALID_OBJECT_DEFINITION),
errmsg("range data types are not binary-compatible")));
if (sourcetyptype == TYPTYPE_ENUM ||
targettyptype == TYPTYPE_ENUM)
ereport(ERROR,
(errcode(ERRCODE_INVALID_OBJECT_DEFINITION),
errmsg("enum data types are not binary-compatible")));
/* /*
* We also disallow creating binary-compatibility casts involving * We also disallow creating binary-compatibility casts involving
* domains. Casting from a domain to its base type is already * domains. Casting from a domain to its base type is already