On tor, 2011-04-21 at 13:39 -0400, Tom Lane wrote: > Josh Berkus <j...@agliodbs.com> writes: > > Better that someone should just focus on whipping Robert's (or was it > > Greg's?) replace-the-missing-casts package into shape as an extension. > > I think Peter originated that, actually. My recollection is that there > didn't seem to be any way to extend it to a complete solution, and > besides which it's really a crutch to avoid fixing bugs in your > application. Still, if someone does want to expend more work on it > I wouldn't object.
http://petereisentraut.blogspot.com/2008/03/readding-implicit-casts-in-postgresql.html There are some problems if you just add *all* the casts back without thinking. In particular, the || appears to be causing problems. But other than those few specific cases, that tool kit fixes all known problems. So anyone who is willing to spend more than zero minutes on planning and executing a major version upgrade shouldn't really have any problems with this aspect. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
