> > I don't think we should expose the offset to user view at all - this is > > just for internal use, no? > > The thing is, physical index numbers has meaning, the logical index > number does not. In a view definition we're going to store the physical > index, not the logical one, for example. We don't want rearranging > columns to invalidate view definitions or plans.
I think we lack a definition here: logical number: the order of columns when doing select * physical number: the position inside the heap tuple (maybe with offset) All views and plans and index definitions and most everyting else needs to reference the logical number. Andreas ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
