From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mark Harris <mharris@esri.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: reading large BYTEA type is slower than expected
Date: Fri, 18 May 2007 13:48:02 -0400
Message-ID: <259.1179510482@sss.pgh.pa.us> (raw)
In-Reply-To: <D7BFFE348C53EF4E8AA0698B1E395FA9085ABD49@flybywire.esri.com>
References: <D7BFFE348C53EF4E8AA0698B1E395FA9085ABD49@flybywire.esri.com>
"Mark Harris" <mharris@esri.com> writes:
> We have recently ported our application to the postgres database. For
> the most part performance has not been an issue; however there is one
> situation that is a problem and that is the initial read of rows
> containing BYTEA values that have an average size of 2 kilobytes or
> greater. For BYTEA values postgres requires as much 3 seconds to read
> the values from disk into its buffer cache.
How large is "large"?
(No, I don't believe it takes 3 sec to fetch a single 2Kb value.)
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, mharris@esri.com
Subject: Re: reading large BYTEA type is slower than expected
In-Reply-To: <259.1179510482@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