Re: random access - bytea

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org>
Cc: Joe Conway <mail(at)joeconway(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: random access - bytea
Date: 2003-10-26 08:32:49
Message-ID: 3F9B86B1.10306@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 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.

It's an index scan, so it's pretty fast...

Chris

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2003-10-26 08:38:21 Coding help
Previous Message Christopher Kings-Lynne 2003-10-26 08:30:15 Re: Timestamp docs weirdness