From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | PFC <lists(at)peufeu(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Bad plan on a view |
Date: | 2006-03-01 18:51:15 |
Message-ID: | 20060301185115.GI82012@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Wed, Mar 01, 2006 at 04:43:53PM +0100, PFC wrote:
>
> >Aren't you going to a lot of work to reinvent something that TOAST
> >already does for you? (At least, in the cases where the text fields
> >are wide enough that it really matters.)
>
> I know. But I have several text fields in the 20 to 200 characters,
> which is too small for toast, but large enough to make up about 90% of the
> table size, which makes it problematic RAM-wise, especially since it's
> gonna grow. Now, if I had 1 big text field, it would be TOASTed and I
> would be happy ;)
Cases like this are why I really wish we had the ability to specify
something other than BLKSZ/4 as when to trigger TOAST. In many cases the
text field is seldom refered to, so getting it out of the main heap is a
big win.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-03-02 18:17:49 | Re: qsort again (was Re: [PERFORM] Strange Create Index behaviour) |
Previous Message | Jim C. Nasby | 2006-03-01 18:48:36 | Re: triggers, performance Was: Re: [GENERAL] rotate records |