Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 7D4DB9F9F0E for ; Fri, 1 Dec 2006 14:16:45 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 65095-08 for ; Fri, 1 Dec 2006 14:16:38 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from lists.commandprompt.com (host-130.commandprompt.net [207.173.203.130]) by postgresql.org (Postfix) with ESMTP id AD2DE9FA12B for ; Fri, 1 Dec 2006 14:16:39 -0400 (AST) Received: from [192.168.1.95] (or-67-76-146-141.sta.embarqhsd.net [67.76.146.141]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id kB1IGdLI011631 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 1 Dec 2006 10:16:40 -0800 Subject: Re: Backup of a big DB with a lot of large objects From: "Joshua D. Drake" To: Richard Broersma Jr Cc: "Milen A. Radev" , pgsql-admin@postgresql.org In-Reply-To: <4617.40027.qm@web31812.mail.mud.yahoo.com> References: <4617.40027.qm@web31812.mail.mud.yahoo.com> Content-Type: text/plain Organization: Command Prompt, Inc. Date: Fri, 01 Dec 2006 10:18:19 -0800 Message-Id: <1164997099.29643.39.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.88.5, clamav-milter version 0.88.5 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Fri, 01 Dec 2006 10:16:40 -0800 (PST) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/7 X-Sequence-Number: 23799 On Fri, 2006-12-01 at 10:06 -0800, Richard Broersma Jr wrote: > > > Replicate it??? > > > > I'm hesitant about replacing backup with replication. It seems to me > > like trying to shoot a mosquito with a cannon. > > One some threads that I've read, some posters mention that once their databases reach a certain > size threshold, backups times become so large that replication seems to be the better perhaps only > choice. It can be but see PITR as well. > > I suppose that if replication is used, one of their child read-only servers can be dedicated the > task of backing up the database thereby relieving that load off of the parent read/write server. Yep, use replication and then backup the slave. > > But this doesn't solve the problem increasing back-up times. Of course, equipping yourself with a > cannon now will really help after your mosquito grows in to an albatross. :o) PITR. Joshua D. Drake > > Regards, > Richard Broersma Jr. > > ---------------------------(end of broadcast)--------------------------- > TIP 7: You can help support the PostgreSQL project by donating at > > http://www.postgresql.org/about/donate > -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate