Matthew Wakeling writes:
> Postgres does not split rows across multiple pages, so this should never
> be a concern. When a row is too big for a page, Postgres will select the
> larger of the columns from the row and compress them. If that fails to
> bring the row size down, then Postgres will s
On Thu, 8 Oct 2009, Michael Gould wrote:
In other SQL engines that I've used, it is recommended that the columns that
are used in
various indexes be placed at the beginning of a row since at some point
(depending on the
engine and/or pagesize) wide rows could end up on other pages. From a
per
In other SQL engines that I've used, it is recommended that the columns that
are used in various indexes be placed at the beginning of a row since at
some point (depending on the engine and/or pagesize) wide rows could end up
on other pages. From a performance standpoint on large tables this makes