X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id AD815D1D2CE for ; Fri, 5 Mar 2004 23:37:48 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 05858-08 for ; Fri, 5 Mar 2004 19:37:49 -0400 (AST) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id A0D52D1D108 for ; Fri, 5 Mar 2004 19:37:46 -0400 (AST) Received: from [63.195.55.98] (HELO 192.168.1.29) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 4549311; Fri, 05 Mar 2004 15:39:00 -0800 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Dennis Bjorklund , Jeff Subject: Re: Fixed width rows faster? Date: Fri, 5 Mar 2004 15:37:02 -0800 User-Agent: KMail/1.5.4 Cc: pgsql-performance@postgresql.org References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200403051537.02535.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/64 X-Sequence-Number: 5920 Jeff: > As far as I know there is only a small win when you want to extract some > field from a tuple and with variable width fields you have to walk to the > correct field. But this is a small performance problem unless you have > very many variable size columns in the table. BTW, Dennis here is not talking about CHAR; CHAR is handled as a variable-length field in Postgres. INTEGER is a fixed-width field. -- -Josh Berkus Aglio Database Solutions San Francisco