Re: random access - bytea

From: Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: random access - bytea
Date: 2003-10-26 05:30:23
Message-ID: Pine.LNX.4.44.0310260624360.23254-100000@zigo.dhs.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, 25 Oct 2003, Joe Conway wrote:

> That will modify the bytea column so that it is stored uncompressed in
> the TOAST table.
>
> Now, simply use substr() to grab any random chunk:
> SELECT substr(foo_bytea, 20000, 100) from foo where foo_id = 42;

This would imply that every little read would have to do a scan on a table
to find the row and then to perform the substr. An open command can
be optimized a lot more, for example to cache entries that have been
opened so that it's fast to read the next 1kb or whatever you want.

Also, the above does not solve writes at all which can also be made
transaction safe and fast with a better api where you can update a part
of a field.

The above is not really a replacement of the current lo-objects.

--
/Dennis

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dennis Bjorklund 2003-10-26 05:50:52 cvs
Previous Message Joe Conway 2003-10-26 05:22:17 Re: random access - bytea