Skip site navigation (1) Skip section navigation (2)

Efficient slicing/substring of TOAST values (for comment)

From: John Gray <jgray(at)azuli(dot)co(dot)uk>
To: pgsql-patches(at)postgresql(dot)org
Subject: Efficient slicing/substring of TOAST values (for comment)
Date: 2001-10-08 13:52:39
Message-ID: 1002549159.23074.40.camel@adzuki (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
Hi all,

I attach a patch which adds access routines for efficient extraction of
parts of TOAST values. 

The principal additions are two routines in tuptoaster.c,
heap_tuple_untoast_attr_slice and toast_fetch_datum_slice. The latter
uses extra index scankeys to retrieve only the TOAST chunks which
contain the requested substring. This will provide a performance benefit
if you repeatedly extract small portions (e.g. file headers) from
TOASTed values, as only one or two chunks will need to be fetched. This
function is only invoked for external, uncompressed storage.

The public access routine (heap_tuple_untoast_attr_slice) does take care
of slicing values that are stored compressed or inline, but doesn't
provide any performance benefit in those cases.

The access macros are in the same vein to existing ones:
for example.

What I haven't done:

1. Documentation. If this patch is appropriate or acceptable, I'll add

2. Changed e.g. textsubstr and byteasubstr to use this method.
textsubstr is complicated by the multibyte support -the fast method is
only applicable in a non-multibyte environment. Also, the SQL negative
offset rule is not embodied in what I've added, and the subscripts are
zero-based. This was on the assumption that if the data was binary (e.g.
JPEG/JFIF data) and the user's intent was to extract the header, it
would be clearer to use zero-based offsets.

3. Added any facility to force a column to have attstorage 'e'. At
present it appears to be defaulted from typstorage, but I couldn't see
any problem with changing it after table creation. Would a keyword to
CREATE TABLE to override the default attstorage be useful? -especially
if the user knew that the data for a column would not be very
compressible (there would be a performance gain in not trying to
compress it, and just storing it externally uncompressed).

Of course, this may just all be useless feature bloat or not up to
scratch coding-wise (and please say so if it is) but please let me know
if it's worth me documenting this or adding any more to it.

(diffs against versions current in CVS as of twenty minutes ago or so)




pgsql-patches by date

Next:From: Tom LaneDate: 2001-10-08 15:06:36
Subject: Re: Efficient slicing/substring of TOAST values (for comment)
Previous:From: Serguei MokhovDate: 2001-10-07 23:48:48
Subject: Place of PO files for NLS (was Re: PG_DUMP NLS (Russian))

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group