On Wed, Jan 12, 2005 at 12:41:38PM -0800, Jeff Davis wrote: > Except then the two heaps would have to be joined somehow for every > operation. It makes sense some times to (if you have a very wide table) > split off the rarely-accessed attributes into a seperate table to be > joined one-to-one when those attributes are needed. To have the system > do that automatically would create problems if the attributes that are > split off are frequently accessed, right?
That mechanism exists right now, and it's called TOAST, dubbed the best thing since sliced bread. We even have documentation for it, new as of our latest RC: http://developer.postgresql.org/docs/postgres/storage-toast.html -- Alvaro Herrera (<[EMAIL PROTECTED]>) "El día que dejes de cambiar dejarás de vivir" ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
