It's a hard balance. In the long haul, you often want people who are careful and diligent and have experience that tempers their urge to jump into things too quickly. But, this type of attitude can actually hurt in startups. In an interview where the particular 3 or 4 things you touch upon are extrapolated (correctly or not) to be the main self-identifying traits of how you work and how you think about problems, if you tell even just one story about superior databases from the 70's or seem to be overly-pedantic when it comes to blowing holes in ideas this can be a 'red flag.'
In a startup environment, I'd rather have the engineer who I think will fall in a hole 3 times and figure out a solution eventually than another who I think will think too hard and fall in one in 3x the time due to their fear built up from previous failures. In an interview, if I am spending my time with the person mostly talking about things that have gone wrong and how everything new is old, I will worry they will be too paralyzed to just hack on and break things -- and this type of focus, while obviously invaluable in many situations, tends to come from more experienced engineers since they have seen more shit go wrong.
"I'm pretty skeptical that many startup entrepreneurs have a "if you're over 40 we don't want to talk to you policy" but instead decide based on 50 year olds coming into their door telling them in their interview how relational databases were figured out in the 70's"
I read it as roughly: "Young entrepreneurs don't have a <40 policy. They're making a rational decision not to hire old people after encountering lots of old people telling them things they think are incorrect because of their age.". Which, I think, we both agree is dumb logic.
[edit; Actually said "sorry" ;-)]