Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 92EAE476FB1; Wed, 22 Jan 2003 19:49:19 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id EF2054770BE; Wed, 22 Jan 2003 19:30:05 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h0N0U45u025726; Wed, 22 Jan 2003 19:30:04 -0500 (EST) To: "Dann Corbit" Cc: "Steve Crawford" , pgsql-performance@postgreSQL.org, pgsql-hackers@postgreSQL.org Subject: Re: Terrible performance on wide selects In-reply-to: References: Comments: In-reply-to "Dann Corbit" message dated "Wed, 22 Jan 2003 16:21:18 -0800" Date: Wed, 22 Jan 2003 19:30:04 -0500 Message-ID: <25725.1043281804@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/861 X-Sequence-Number: 34471 "Dann Corbit" writes: > For the disk case, why not have the start of the record contain an array > of offsets to the start of the data for each column? It would only be > necessary to have a list for variable fields. No, you'd need an entry for *every* column (or at least, every one to the right of the first variable-width column or NULL). That's a lot of overhead, especially in comparison to datatypes like bool or int4 ... regards, tom lane