From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dann Corbit <DCorbit@connx.com>
Cc: Steve Crawford <scrawford@pinpointresearch.com>
Cc: pgsql-performance@postgreSQL.org
Cc: pgsql-hackers@postgreSQL.org
Subject: Re: Terrible performance on wide selects
Date: Wed, 22 Jan 2003 19:04:02 -0500
Message-ID: <25521.1043280242@sss.pgh.pa.us> (raw)
In-Reply-To: <D90A5A6C612A39408103E6ECDD77B8294CD85F@voyager.corporate.connx.com>
References: <D90A5A6C612A39408103E6ECDD77B8294CD85F@voyager.corporate.connx.com>
"Dann Corbit" <DCorbit@connx.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, DCorbit@connx.com, scrawford@pinpointresearch.com, pgsql-hackers@postgreSQL.org
Subject: Re: Terrible performance on wide selects
In-Reply-To: <25521.1043280242@sss.pgh.pa.us>
References: <D90A5A6C612A39408103E6ECDD77B8294CD85F@voyager.corporate.connx.com> <25521.1043280242@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox