This is related to, but has a different impact than #18437.
18437 and its fix focused on row signature flapping, which can cause queries to use incorrect columns at query planning time when column analysis errors occur.
This issue, however, focuses on type correctness problems that arise when column analysis errors cause a fallback to string types.
The root cause of this behavior is still unclear. There is some discussion in #19162 (comment).
It will be good to detect these types more accurately rather than fallback to string type when there are column analyses errors.
Affected Version
32.0.1 (likely affects later versions as well)