Should this case at heaptuple.c:1606 be turned into an elog() now that we have
plan cache invalidation? If it "can't" happen then it's probably better that
we find out if it does happen rather than silently run the old plan and return

         * If the attribute's column has been dropped, we force a NULL result.
         * This case should not happen in normal use, but it could happen if we
         * are executing a plan cached before the column was dropped.
        if (tupleDesc->attrs[attnum - 1]->attisdropped)
                *isnull = true;
                return (Datum) 0;

  Gregory Stark

---------------------------(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

Reply via email to