X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 4C9BCD90E3 for ; Mon, 10 Oct 2005 09:57:01 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 43057-02 for ; Mon, 10 Oct 2005 12:56:56 +0000 (GMT) Received: from ucsns.ucs.co.za (ucsns.ucs.co.za [196.23.43.2]) by svr1.postgresql.org (Postfix) with ESMTP id 606B4D8D8D for ; Mon, 10 Oct 2005 09:56:58 -0300 (ADT) Received: from ucspost.ucs.co.za (mailgw1.ucs.co.za [196.23.43.253]) by ucsns.ucs.co.za (Postfix) with ESMTP id DE5242BD6B; Mon, 10 Oct 2005 14:57:01 +0200 (SAST) Received: from jhb.ucs.co.za (jhb.ucs.co.za [172.31.1.3]) by ucspost.ucs.co.za (Postfix) with ESMTP id E637CD9DF4; Mon, 10 Oct 2005 14:57:01 +0200 (SAST) Received: from svb.ucs.co.za (svb.ucs.co.za [172.31.1.148]) by jhb.ucs.co.za (Postfix) with ESMTP id 153DE977D8; Mon, 10 Oct 2005 14:57:01 +0200 (SAST) Date: Mon, 10 Oct 2005 14:57:00 +0200 From: Stef To: Tino Wildenhain Cc: pgsql-performance@postgresql.org Subject: Re: Compression of text columns Message-ID: <20051010145700.586dc488@svb.ucs.co.za> In-Reply-To: <434A5E22.9040500@wildenhain.de> References: <20051010141721.0bebbaa7@svb.ucs.co.za> <434A5E22.9040500@wildenhain.de> X-Mailer: Sylpheed-Claws 1.9.6cvs1 (GTK+ 2.6.10; i486-pc-linux-gnu) User-Agent: sillypheed-claws (anti-aliased) X-Face: +lU/o'$=Zv9%Xjo]Kq[_{n&Kb`f{YEWH4&Y#M]'6BkD?VoWe#*@S\MWyD'I>s:0v4{#\[J]l*?]t2uaO(j$d*77Ca-UHo.tkl2)0$B3Jxww\o:xor]<:*Yfx9Vceh)9I/'2g\RKhGTxIIsR^ke^`LVeZ9ksb*:$kQeR@ X-Operating-System: sid X-X-X: _-^-_ Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.133 required=5 tests=[AWL=0.133] X-Spam-Level: X-Archive-Number: 200510/164 X-Sequence-Number: 14932 Tino Wildenhain mentioned : => Well, text columns are automatically compressed via the toast mechanism. => This is handled transparently for you. OK, I misread the documentation, and I forgot to mention that I'm using postgres 7.3 and 8.0 It's actually the EXTERNAL storage type that is larger, not EXTENDED. What kind of compression is used in the EXTERNAL storage type? Is there any way to achieve better compression?