X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id A85A49FA1A4 for ; Thu, 8 Jun 2006 13:33:48 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 78776-01 for ; Thu, 8 Jun 2006 13:33:43 -0300 (ADT) 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 813519FA5DD for ; Thu, 8 Jun 2006 13:33:43 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id 60A1256445; Thu, 8 Jun 2006 11:33:42 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Thu, 8 Jun 2006 11:33:41 -0500 Date: Thu, 8 Jun 2006 11:33:41 -0500 From: "Jim C. Nasby" To: Tom Lane Cc: Ludek Finstrle , pgsql-admin@postgresql.org Subject: Re: Maximum text and bytea size? Message-ID: <20060608163341.GS45331@pervasive.com> References: <20060608091802.GA32622@soptik.pzkagis.cz> <20060608153750.GN45331@pervasive.com> <28212.1149782102@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <28212.1149782102@sss.pgh.pa.us> 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:060608:tgl@sss.pgh.pa.us::1kGFJW9brOduW/TS:00000000000000000000 0000000000000000000000001w0F X-Hashcash: 1:20:060608:luf@pzkagis.cz::5JWSGia1XeCuJFo6:0004Pvg X-Hashcash: 1:20:060608:pgsql-admin@postgresql.org::/7McO11Ol6XuAgyq:00000000000 0000000000000000000000000T7R X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/61 X-Sequence-Number: 22023 On Thu, Jun 08, 2006 at 11:55:02AM -0400, Tom Lane wrote: > "Jim C. Nasby" writes: > > On Thu, Jun 08, 2006 at 11:18:02AM +0200, Ludek Finstrle wrote: > >> I read this value in TOAST section. Is my opinion correct? > > > From http://www.postgresql.org/docs/8.1/interactive/storage-toast.html: > > "TOAST usurps the high-order two bits of the varlena length word, > > thereby limiting the logical size of any value of a TOAST-able data type > > to 1Gb (2^30 - 1 bytes)." > > > There was a proposal made some time ago to allow for a variable-length > > length word format, where one of the bits in each word would specify > > that there was an additional length word. > > Hm, I don't remember that. It seems rather pointless, as I'm quite sure > that the *practical* limit is a great deal less than 1Gb. Has anyone > done any performance testing of GB-sized toasted values? Given how toasted data is currently stored, you're probably correct. If it was switched to a binary format that didn't have all the table/tuple overheard (which I seem to recall a discussion about), it could be a very different story. -- 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