X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 08261D1D12E for ; Wed, 31 Mar 2004 00:20:38 +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 54603-06 for ; Tue, 30 Mar 2004 20:20:39 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 41749D1B8CA for ; Tue, 30 Mar 2004 20:20:36 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i2V0KaYn048984 for ; Wed, 31 Mar 2004 00:20:36 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i2UNuq5m028029 for pgsql-admin@postgresql.org; Tue, 30 Mar 2004 23:56:52 GMT From: louisducnguyen@hotmail.com (louis nguyen) X-Newsgroups: comp.databases.ms-sqlserver, comp.databases.postgresql.admin, cz.comp.microsoft.sql, microsoft.public.il.hebrew.sqlserver, microsoft.public.sqlserver, microsoft.public.sqlserver.misc Subject: Re: what is the impact of Database size on Performemce Date: 30 Mar 2004 15:56:54 -0800 Organization: http://groups.google.com Lines: 18 Message-ID: References: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: groups-abuse@google.com To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/67 X-Sequence-Number: 13040 > 1. Is there any impact? > 2. Does one very large table impact the performence of the the whole DB, > meaning the overall performence and access the other tables. > 3. What are the ways to reduce the impact of the DB size on the DB > performence I've run into 2 problems w/ very large DB. A) Backups. I have a 50G DB. I backup to file then delete yesterday's backup file (I have another process which transfers the backup file to tape). So I have a 50G backup file and I need another 50G freespace, to run my backup process. B) Reindexing. On any given day maybe 5% (max) of new data is added to my DB. But DBCC reindex has to work on all the indexes. So DBCC reindex takes 3 hours a night. Yuck. Maybe there is a better way. But I try to keep each database as small as possible.