Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 3D7879FA17F for ; Thu, 30 Nov 2006 16:19:22 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 16193-10 for ; Thu, 30 Nov 2006 16:19:09 -0400 (AST) X-Greylist: delayed 00:14:54.850989 by SQLgrey-1.7.4 Received: from server.firetrust.net (mailserver.firetrust.com [209.213.221.13]) by postgresql.org (Postfix) with ESMTP id 5A66F9FA170 for ; Thu, 30 Nov 2006 16:19:09 -0400 (AST) Received: from localhost.localdomain (203-97-61-135.dsl.clear.net.nz [203.97.61.135]) by server.firetrust.net (8.13.8/8.13.8) with SMTP id kAUK49Sm020520 for ; Fri, 1 Dec 2006 09:04:11 +1300 Date: Fri, 1 Dec 2006 09:04:09 +1300 From: Steve Holdoway To: pgsql-admin@postgresql.org Subject: Re: Backup of a big DB with a lot of large objects Message-Id: <20061201090409.d3dcfd44.steve.holdoway@firetrust.com> In-Reply-To: <32c009ea0611300812p4e5ed4acvf45537d1c70dfea0@mail.gmail.com> References: <32c009ea0611300812p4e5ed4acvf45537d1c70dfea0@mail.gmail.com> Organization: Firetrust Ltd X-Mailer: Sylpheed version 2.2.6 (GTK+ 2.8.20; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV devel-20061113/2264/Fri Dec 1 08:13:30 2006 on server.firetrust.net X-Virus-Status: Clean X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/264 X-Sequence-Number: 23791 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? > > -- > Milen A. Radev > > ---------------------------(end of broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster Replicate it???