This is a table with just one entry created to test the problem. Should
not have any indexing issues.
I've since isolated the problem to the unescape_bytea function not the
I inserted the same image to a bytea column using base64 encoding, and
extracted it from the table (using base64 decoding) and this worked very
fast (<1 second). So, it is the unescape_bytea function that is to blame.
Hope that helps,
Kalador Entertainment Inc.
Alvaro Herrera wrote:
>Kai Ronan wrote:
>> // Get the bytea data
>> $res = pg_query("SELECT data FROM image WHERE name='big.gif'");
>Do you have an index in the image.name column? What does an
>EXPLAIN ANALYZE SELECT data FROM image WHERE name='big.gif'
In response to
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2006-02-05 00:40:26|
|Subject: Re: BUG #2237: SELECT optimizer drops everything improperly |
|Previous:||From: Alvaro Herrera||Date: 2006-02-04 22:21:57|
|Subject: Re: BUG #2236: extremely slow to get unescaped bytea data from db|