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 40014D1B45F for ; Tue, 25 Nov 2003 19:23:50 +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 22406-01 for ; Tue, 25 Nov 2003 15:23:18 -0400 (AST) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id DB17BD1B434 for ; Tue, 25 Nov 2003 15:23:17 -0400 (AST) Received: from [66.219.92.2] (HELO temoku) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3977127; Tue, 25 Nov 2003 11:23:50 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: shane hill , pgsql-performance Subject: Re: design question: general db performance Date: Tue, 25 Nov 2003 11:12:47 -0800 User-Agent: KMail/1.4.3 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-Transfer-Encoding: quoted-printable Message-Id: <200311251112.47473.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/245 X-Sequence-Number: 4805 Shane, > Disclaimer: I am relatively new to RDBMSs, so please do not laugh at me= =20 > too loudly, you can laugh, just not too loudly and please do not point. = :) Hey, we all started somewhere. Nobody was born knowing databases. Except= =20 maybe Neil Conway. > I am working on an Automated Installer Testing System for Adobe Systems= =20 > and I am doing a DB redesign of the current postgres db: Cool! We're going to want to talk to you about a case study later, if yo= u=20 can get your boss to authorize it .... > Our db is getting to be a respectable size (about 10GB right now) and is= =20 > growing slower and slower.=20 Slower and slower? Hmmm ... what's your VACUUM. ANALYZE & REINDEX schedul= e?=20=20 What PG version? What are your postgresql.conf settings? Progressive=20 performance loss may indicate a problem with one or more of these things ... > then in my data I would just store 1,2,3 or 4 instead of the whole=20 > permissions string. >=20 > it seems to me that we would save lots of space and over time not see=20 > the same performance degradation. Yes, this is a good idea. Abstracting other repetitive data is good too.= =20=20 Also keep in mind that the permissions themselves can be represented as oct= al=20 numbers instead of strings, which takes less space. --=20 -Josh Berkus Aglio Database Solutions San Francisco