Suppose I have a table - lets say it was developed by someone with little or no
understanding of database design - and it has 230 columns.
Now, it turns out that 99% of the time only about 8 colums are required, but
all 230 columns are populated. However, legacy applications (which are run
Tom Lane [EMAIL PROTECTED] wrote: John Sales writes:
By doing this, I'm hoping that the query optimizer is smart enough to see
that if a query comes in and requests only the six columns (that are in the
narrower table) that PostgreSQL won't have to load the wider table into the
buffer pool
