Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 82BD7476EF4; Thu, 23 Jan 2003 05:56:09 -0500 (EST) Received: from dcave.digsys.bg (dcave.digsys.bg [192.92.129.5]) by postgresql.org (Postfix) with ESMTP id 4AAA14765DD; Thu, 23 Jan 2003 05:49:56 -0500 (EST) Received: from dcave.digsys.bg (daniel@localhost.digsys.bg [127.0.0.1]) by dcave.digsys.bg (8.11.6/8.10.1) with ESMTP id h0NAi8Y21333; Thu, 23 Jan 2003 12:44:12 +0200 (EET) Message-Id: <200301231044.h0NAi8Y21333@dcave.digsys.bg> X-Mailer: exmh version 2.1.0 09/18/1999 To: Hannu Krosing Cc: Tom Lane , Dann Corbit , Steve Crawford , pgsql-performance@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: Terrible performance on wide selects In-reply-to: Your message of "23 Jan 2003 12:30:48 +0200." <1043317847.2347.35.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Jan 2003 12:44:04 +0200 From: Daniel Kalchev X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/875 X-Sequence-Number: 34485 >>>Hannu Krosing said: > Tom Lane kirjutas N, 23.01.2003 kell 02:04: > > We already do cache column offsets when they are fixed. The code that's > > the problem executes when there's a variable-width column in the table > > --- which means that all columns to its right are not at fixed offsets, > > and have to be scanned for separately in each tuple, AFAICS. > > Not only varlen columns, but also NULL columns forbid knowing the > offsets beforehand. Does this mean, that constructing tables where fixed length fields are 'before' variable lenght fields and 'possibly null' fields might increase performance? Daniel