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

Re: TOAST usage setting

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Bruce Momjian" <bruce(at)momjian(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: TOAST usage setting
Date: 2007-05-29 17:06:47
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
"Bruce Momjian" <bruce(at)momjian(dot)us> writes:

>> No, we did substring() too :)
> Uh, I looked at text_substring(), and while there is an optimization to
> do character counting for encoding length == 1, it is still accessing
> the data.

Sure but it'll only access the first chunk. There are two chunks in your test.
It might be interesting to run tests accessing 0 (length()), 1 (substr()), and
2 chunks (hashtext()).

Or if you're concerned with the cpu cost of hashtext you could calculate the
precise two bytes you need to access with substr to force it to load both
chunks. But I think the real cost of unnecessary toasting is the random disk
i/o so the cpu cost is of secondary interest.

  Gregory Stark

In response to


pgsql-hackers by date

Next:From: Bruce MomjianDate: 2007-05-29 17:19:07
Subject: Re: TOAST usage setting
Previous:From: Gregory StarkDate: 2007-05-29 17:02:51
Subject: Re: Concurrent psql patch

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