Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 22295475FB0 for ; Thu, 23 Jan 2003 09:52:46 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 2669A476FAE for ; Thu, 23 Jan 2003 09:50:24 -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 h0NEo25u025739; Thu, 23 Jan 2003 09:50:03 -0500 (EST) To: Daniel Kalchev Cc: Hannu Krosing , Dann Corbit , Steve Crawford , pgsql-performance@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: Terrible performance on wide selects In-reply-to: <200301231044.h0NAi8Y21333@dcave.digsys.bg> References: <200301231044.h0NAi8Y21333@dcave.digsys.bg> Comments: In-reply-to Daniel Kalchev message dated "Thu, 23 Jan 2003 12:44:04 +0200" Date: Thu, 23 Jan 2003 09:50:02 -0500 Message-ID: <25738.1043333402@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/883 X-Sequence-Number: 34493 Daniel Kalchev writes: > Does this mean, that constructing tables where fixed length fields are > 'before' variable lenght fields and 'possibly null' fields might increase > performance? There'd have to be no nulls, period, to get any useful performance difference --- but yes, in theory putting fixed-length columns before variable-length ones is a win. I wouldn't bother going out to rearrange your schemas though ... at least not before you do some tests to prove that it's worthwhile. regards, tom lane