X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 0AEFDD1B47A for ; Tue, 25 Nov 2003 19:28:32 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 21190-09 for ; Tue, 25 Nov 2003 15:28:00 -0400 (AST) Received: from anchor-post-32.mail.demon.net (anchor-post-32.mail.demon.net [194.217.242.90]) by svr1.postgresql.org (Postfix) with ESMTP id 6381ED1B434 for ; Tue, 25 Nov 2003 15:27:44 -0400 (AST) Received: from mwynhau.demon.co.uk ([193.237.186.96] helo=mainbox.archonet.com) by anchor-post-32.mail.demon.net with esmtp (Exim 3.35 #1) id 1AOiqd-0000Hj-0W; Tue, 25 Nov 2003 19:27:43 +0000 Received: by mainbox.archonet.com (Postfix, from userid 529) id D42AE17DE4; Tue, 25 Nov 2003 19:27:41 +0000 (GMT) Received: from client17.archonet.com (client17.archonet.com [192.168.1.17]) by mainbox.archonet.com (Postfix) with ESMTP id 190DB179A4; Tue, 25 Nov 2003 19:27:40 +0000 (GMT) From: Richard Huxton To: shane hill , pgsql-performance Subject: Re: design question: general db performance Date: Tue, 25 Nov 2003 19:27:39 +0000 User-Agent: KMail/1.5 References: <3FC26E96.9090101@be-a-part.de> <3FC27071.9000001@bigfoot.com> <3FC3A2A7.6060804@adobe.com> In-Reply-To: <3FC3A2A7.6060804@adobe.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200311251927.39671.dev@archonet.com> X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=0.15.3 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/247 X-Sequence-Number: 4807 On Tuesday 25 November 2003 18:42, shane hill wrote: > > Our db is getting to be a respectable size (about 10GB right now) and is > growing slower and slower. I have been charged with making it faster and > with a smaller footprint while retaining all of the current > functionality. here is one of my ideas. Please tell me if I am crazy: Your idea of using an integer makes sense - that's how it is stored on unix anyway. Are you familiar with VACUUM/VACUUM FULL/REINDEX and when you should use them? If not, that's a good place to start. Try a VACUUM FULL on frequently updated tables and see if that reduces your disk size. You'll probably want to check the performance notes too: http://www.varlena.com/varlena/GeneralBits/Tidbits/index.php -- Richard Huxton Archonet Ltd