From: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Scott Cain <cain(at)cshl(dot)org>, PgSQL Performance ML <pgsql-performance(at)postgresql(dot)org>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: [SQL] EXTERNAL storage and substring on long strings |
Date: | 2003-08-14 18:55:38 |
Message-ID: | 3F3BDB2A.40506@Yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance pgsql-sql |
Tom Lane wrote:
> Jan Wieck <JanWieck(at)Yahoo(dot)com> writes:
>> Doesn't look that unrealistic to me. A plain text based substring
>> function will reassemble the whole beast first before cutting out the
>> wanted part. His manually chunked version will read only those chunks
>> needed.
>
> So does substr(), if applied to EXTERNAL (non-compressed) toasted text.
> See John Gray's improvements a release or two back.
Duh ... of course, EXTERNAL is uncompressed ... where do I have my head?
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-08-14 19:28:04 | Re: Vacuum performance question |
Previous Message | Scott Cain | 2003-08-14 18:11:07 | Re: [SQL] EXTERNAL storage and substring on long strings |
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory S. Williamson | 2003-08-14 23:46:08 | lower/upper functions and strings in searches |
Previous Message | krystoffff | 2003-08-14 18:14:46 | Re: How to optimize this query ? |