I'm working on my upgrade process and inadvertantly took my test site to 7.4.33. When I went to check the site, my collab system was giving a problem with request. The webgui log had this in it:
FATAL - mysite - main::[[undef]] - Couldn't execute prepared statement: SELECT SQL_CALC_FOUND_ROWS
            asset.assetId,
            asset.className,
            assetData.revisionDate as revisionDate
        from Thread
            left join asset on Thread.assetId=asset.assetId
            left join Post on Post.assetId=Thread.assetId and Thread.revisionDate = Post.revisionDate
            left join assetData on assetData.assetId=Thread.assetId and Thread.revisionDate = assetData.revisionDate
        where
            asset.parentId='kIJjAYgZizu8RjypIZ1V1w'
            and asset.state='published'
            and asset.className='WebGUI::Asset::Post::Thread'
            and assetData.revisionDate=(
                select
                    max(revisionDate)
                from
                    assetData
                where
                    assetData.assetId=asset.assetId
                    and (status='approved' or status='archived')
            )
            and status='approved'
        group by
            assetData.assetId
        order by
            Thread.isSticky desc,
        `dateUpdated`
            desc LIMIT 0,30 : With place holders: .  Root cause: Unknown column 'dateUpdated' in 'order clause'

I backed out the change and then only upgraded to 7.3.32, and did not have the problem. I haven't had a chance to attempt to duplicate the problem, so I'm not sure if it is specific to my site or more general. Susan B

Unless you specifically tell it to not clear the cache, it will by default.

This is definitely a bug. The upgrade script is not clearing the cache. After upgrading from 7.3.22 to 7.4.32 on multiple sites/databases, I've had to immediately go into the admin console and manually clear the cache to get multiple collabs to not display an error.