Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 3F186476FBA; Wed, 22 Jan 2003 19:28:12 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 3125947610E; Wed, 22 Jan 2003 19:04:03 -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 h0N0435u025522; Wed, 22 Jan 2003 19:04:03 -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 15:56:55 -0800" Date: Wed, 22 Jan 2003 19:04:02 -0500 Message-ID: <25521.1043280242@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/853 X-Sequence-Number: 34463 "Dann Corbit" writes: > Maybe I don't really understand the problem, but it seems simple enough > to do it once for the whole query. 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. regards, tom lane