"Tom Lane" <[EMAIL PROTECTED]> writes: > Gregory Stark <[EMAIL PROTECTED]> writes: >> Should this case at heaptuple.c:1606 be turned into an elog() now that we >> have >> plan cache invalidation? > > No, I think it's good as-is. Reading the column as null is the correct > behavior.
Isn't the correct behaviour that you would have been prevented from executing that plan and forced to replan your query? Let me put it another way, how would I write a test case to cover these lines of code and not receive an error from replanning? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
