pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Disallow creating binary-coercible casts involving range types. 2+ messages / 1 participants [nested] [flat]
* pgsql: Disallow creating binary-coercible casts involving range types. @ 2024-08-21 16:00 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 2+ messages in thread From: Tom Lane @ 2024-08-21 16:00 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Disallow creating binary-coercible casts involving range types. 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 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/86488cdf1249f86cff75c2446f670be49cb55055 Modified Files -------------- src/backend/commands/functioncmds.c | 35 ++++++++++++++++++++++++----------- 1 file changed, 24 insertions(+), 11 deletions(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
* pgsql: Disallow creating binary-coercible casts involving range types. @ 2024-08-21 16:00 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 2+ messages in thread From: Tom Lane @ 2024-08-21 16:00 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Disallow creating binary-coercible casts involving range types. 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 Branch ------ REL_17_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/2366ab246a32fa2f10523768926dcf6afe42080f Modified Files -------------- src/backend/commands/functioncmds.c | 35 ++++++++++++++++++++++++----------- 1 file changed, 24 insertions(+), 11 deletions(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2024-08-21 16:00 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2024-08-21 16:00 pgsql: Disallow creating binary-coercible casts involving range types. Tom Lane <tgl@sss.pgh.pa.us> 2024-08-21 16:00 pgsql: Disallow creating binary-coercible casts involving range types. Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox