X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id B17BD9DC863 for ; Wed, 1 Mar 2006 14:51:17 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 60495-08 for ; Wed, 1 Mar 2006 14:51:17 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 9838E9DC821 for ; Wed, 1 Mar 2006 14:51:15 -0400 (AST) Received: by noel.decibel.org (Postfix, from userid 1001) id 66C4B56457; Wed, 1 Mar 2006 12:51:16 -0600 (CST) Received: (hashcash-sendmail, from uid 1001); Wed, 1 Mar 2006 12:51:15 -0600 Date: Wed, 1 Mar 2006 12:51:15 -0600 From: "Jim C. Nasby" To: PFC Cc: Tom Lane , pgsql-performance@postgresql.org Subject: Re: Bad plan on a view Message-ID: <20060301185115.GI82012@pervasive.com> References: <10652.1141226168@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 6.0-RELEASE-p4 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Hashcash: 1:20:060301:lists@peufeu.com::7m3m4r87TDDg+5Ij:008ad X-Hashcash: 1:20:060301:tgl@sss.pgh.pa.us::qS5wBHmN+o9xJzIt:00000000000000000000 0000000000000000000000005TTc X-Hashcash: 1:20:060301:pgsql-performance@postgresql.org::4JCczso0nwbxdKIU:00000 0000000000000000000000002GFt X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.109 required=5 tests=[AWL=0.109] X-Spam-Score: 0.109 X-Spam-Level: X-Archive-Number: 200603/12 X-Sequence-Number: 17449 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