Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 239809FA0FB for ; Thu, 30 Nov 2006 12:13:07 -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 44091-09 for ; Thu, 30 Nov 2006 12:12:34 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by postgresql.org (Postfix) with ESMTP id A275F9F9ECF for ; Thu, 30 Nov 2006 12:12:33 -0400 (AST) Received: by ug-out-1314.google.com with SMTP id k3so1938420ugf for ; Thu, 30 Nov 2006 08:12:32 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=bo0/in7fNlD6I/+vSIF6S+MCQ3dy9UY0WypjZVAtUTq5QTrt4xAP4pwGTUn/+CmX5eTLd+PMN6U3u6U7nGx1Muf8DqKQkP/7QuyoGLDxF0/XJJRflhDPtJt5xnLBJSc8znMzbhyUnU89R7UjvvnLOIN+F0pTnzxq+lxGjL8vIUY= Received: by 10.78.20.13 with SMTP id 13mr3666814hut.1164903151705; Thu, 30 Nov 2006 08:12:31 -0800 (PST) Received: by 10.78.175.2 with HTTP; Thu, 30 Nov 2006 08:12:31 -0800 (PST) Message-ID: <32c009ea0611300812p4e5ed4acvf45537d1c70dfea0@mail.gmail.com> Date: Thu, 30 Nov 2006 18:12:31 +0200 From: "Milen A. Radev" To: pgsql-admin@postgresql.org Subject: Backup of a big DB with a lot of large objects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Google-Sender-Auth: 4c3e78ad578a7bbd X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/263 X-Sequence-Number: 23790 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