Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 55D9A2E4338 for ; Wed, 16 Jan 2008 21:02:28 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 61616-03 for ; Wed, 16 Jan 2008 21:01:57 -0400 (AST) Received: from mail.jobflash.com (mail.jobflash.com [67.108.12.41]) by postgresql.org (Postfix) with ESMTP id DDD722E4334 for ; Wed, 16 Jan 2008 21:02:01 -0400 (AST) Received: from [192.168.1.65] (adsl-76-204-77-34.dsl.pltn13.sbcglobal.net [76.204.77.34]) by mail.jobflash.com (Postfix) with ESMTP id 3AC3A420C4; Wed, 16 Jan 2008 17:02:00 -0800 (PST) Message-ID: <478EA908.9040607@jobflash.com> Date: Wed, 16 Jan 2008 17:02:00 -0800 From: Tom Arthurs User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Tom Davies Cc: pgsql-admin@postgresql.org Subject: Re: Backup of live database References: <5a9699850801152257g6ee9513i6c4fc88a5f20a785@mail.gmail.com> <478DAC1D.3010909@commandprompt.com> <5a9699850801152310g39fa9bf3y3926892145ab3dcf@mail.gmail.com> <478DBAC3.8050802@commandprompt.com> <5a9699850801160024y7abdcd2fjdb1035c2070797eb@mail.gmail.com> <478E4214.6030805@jobflash.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/196 X-Sequence-Number: 27970 If you don't start archiving log files, your first backup won't be valid -- well I suppose you could do it the hard way and start the backup and the log archiving at exactly the same time (can't picture how to time that), but the point is you need the current log when you kick off the backup. If you kick off archiving first, you are assured of a valid backup (when the recovery is done.) You may get some extra log files that way, but better too many than too few. (been there, done that.) Tom Davies wrote: > > On 17/01/2008, at 4:42 AM, Tom Arthurs wrote: >> The important thing is to start archiving the WAL files *prior* to the >> first OS backup, or you will end up with an unusable data base. > > Why does the recovery need WAL files from before the backup? > > Tom > > ---------------------------(end of broadcast)--------------------------- > TIP 3: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq > >