Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 6392D9F9392 for ; Fri, 1 Dec 2006 13:29:48 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 50823-07 for ; Fri, 1 Dec 2006 13:29:38 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by postgresql.org (Postfix) with ESMTP id 766D69FA282 for ; Fri, 1 Dec 2006 13:29:39 -0400 (AST) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GqCC2-0004QY-99 for pgsql-admin@postgresql.org; Fri, 01 Dec 2006 18:28:58 +0100 Received: from pirus.securax.be ([213.16.46.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 01 Dec 2006 18:28:58 +0100 Received: from milen by pirus.securax.be with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 01 Dec 2006 18:28:58 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: pgsql-admin@postgresql.org From: "Milen A. Radev" Subject: Re: Backup of a big DB with a lot of large objects Date: Fri, 01 Dec 2006 19:28:08 +0200 Lines: 25 Message-ID: References: <32c009ea0611300812p4e5ed4acvf45537d1c70dfea0@mail.gmail.com> <20061201090409.d3dcfd44.steve.holdoway@firetrust.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: pirus.securax.be User-Agent: Mozilla Thunderbird 1.5.0.8 (Windows/20061025) In-Reply-To: <20061201090409.d3dcfd44.steve.holdoway@firetrust.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.063 tagged_above=0 required=5 tests=AWL, BAYES_40, RCVD_IN_SORBS_WEB, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200612/4 X-Sequence-Number: 23796 Steve Holdoway написа: > On Thu, 30 Nov 2006 18:12:31 +0200 > "Milen A. Radev" wrote: > >> We have a big DB that's backuped nightly using pg_dump in the custom >> format. Most of its size are several thousand large objects. During >> the dump of those LO the machine is heavily loaded so we are looking >> for a way to "optimise" that part of backup process. We had an idea to >> backup the DB but without the LO and to dump nightly only those LO >> that were changed or added since the last backup. Unfortunately in >> v8.1 (we use 8.1.5) there is no way to dump a whole database without >> the LO. >> >> Any ideas for a less taxing backup process? >> [..] > > Replicate it??? I'm hesitant about replacing backup with replication. It seems to me like trying to shoot a mosquito with a cannon. -- Milen A. Radev