From: Jim C. Nasby <jnasby@pervasive.com>
To: PFC <lists@peufeu.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Bad plan on a view
Date: Wed, 1 Mar 2006 12:51:15 -0600
Message-ID: <20060301185115.GI82012@pervasive.com> (raw)
In-Reply-To: <op.s5qrbf17cigqcu@apollo13>
References: <op.s5qo4bx8cigqcu@apollo13>
<10652.1141226168@sss.pgh.pa.us>
<op.s5qrbf17cigqcu@apollo13>
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@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: jnasby@pervasive.com, lists@peufeu.com, tgl@sss.pgh.pa.us
Subject: Re: Bad plan on a view
In-Reply-To: <20060301185115.GI82012@pervasive.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox