Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 58C382E005A for ; Mon, 28 Apr 2008 17:59:08 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 98377-06 for ; Mon, 28 Apr 2008 17:59:02 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.181]) by developer.postgresql.org (Postfix) with ESMTP id 0094F2E0040 for ; Mon, 28 Apr 2008 17:59:01 -0300 (ADT) Received: by el-out-1112.google.com with SMTP id j27so1711091elf.23 for ; Mon, 28 Apr 2008 13:59:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=JzCjfiISk0j0Bo5nes6kXxRajf35SYMp6OTK04PHjUM=; b=KbLN5iaCZICBNBCJgpWmi5hZoQe7x8iyCgCzyp6vOvyRrPpkmLTErUv+cZsugCPWJaYovcV6Un+XAMdIpjBstO6iHtUhZRG7DpJKhrF+hyXuJW7rU5DekwZeud5Vmm75377msOd8a5pg2LwLuMzPRfWl35Jmlz+sLe0zUJL93sE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=EwBQT1y2d6NVSrUqDk0gpxrJmo8mhIZjeHDe5SaKLd4ii/Kts9Wml5CCG1tBmPrJK+6wPF+B/Bice3ItZddx8gG4uDrlSbgEklw5HaZLjYWHqYOz4i4oD7Z3wx3RXSxUuXHdcOHhMFO/QzSbthIiA1LMtAOsErdvjJQn/v5HvCQ= Received: by 10.142.238.12 with SMTP id l12mr23821wfh.33.1209416339296; Mon, 28 Apr 2008 13:58:59 -0700 (PDT) Received: by 10.143.188.6 with HTTP; Mon, 28 Apr 2008 13:58:59 -0700 (PDT) Message-ID: Date: Mon, 28 Apr 2008 16:58:59 -0400 From: "Radhika S" To: pgsql-performance@postgresql.org Subject: Re: Replication Syatem In-Reply-To: <7e4ba9550804280638ie81dc23w472785c83cd38fcf@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <7e4ba9550804280638ie81dc23w472785c83cd38fcf@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.899 tagged_above=0 required=5 tests=FS_REPLICA=1.179, SARE_SPEC_REPLICA=0.72 X-Spam-Level: * X-Archive-Number: 200804/415 X-Sequence-Number: 29908 On Mon, Apr 28, 2008 at 9:38 AM, Gauri Kanekar wrote: > All, > > We have a table "table1" which get insert and updates daily in high numbers, > bcoz of which its size is increasing and we have to vacuum it every > alternate day. Vacuuming "table1" take almost 30min and during that time the > site is down. Slony is an open source replication system built for Postgres. But the real problem is that you are doing a vaccum full every day. This is highly invasive. Take a look at the postgres docs on Vacuuming the db. Analyze is best on a daily basis. If you have a lot of deletes, then try vacuum truncate. The postgres documentation describes the various vaccuum options and explains the merits of each. Hope that helps. Radhika -- It is all a matter of perspective. You choose your view by choosing where to stand. --Larry Wall