Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 016E864FCF3 for ; Wed, 27 Aug 2008 17:49:19 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 92057-03 for ; Wed, 27 Aug 2008 17:49:12 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from web36904.mail.mud.yahoo.com (web36904.mail.mud.yahoo.com [209.191.85.72]) by postgresql.org (Postfix) with SMTP id 97C0464FCDA for ; Wed, 27 Aug 2008 17:49:15 -0300 (ADT) Received: (qmail 70725 invoked by uid 60001); 27 Aug 2008 20:49:13 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=WexOc6gK6IONixPbeU8Vv7A1wPwywMizqIE9NaW0q0VyhSDfFrMeK6XbAaSTpIzy61h+sQgapuXSmdfUxI9v3I0fBGvpcbQbyVzfPWpfGLwqlNZdb4STTfebapKVfNA5zhZKXD9I50IWiDa4yWEeVrONl2B/fNw7rd3pK6p6xN0=; X-YMail-OSG: EqciLuEVM1khvK_4oJ8kg1_PhsKe8xqoPu6QjvdJdgpo0szB1Dvv.eFlqJq4eMMituXhSOSxlNo34VNCqb41bAQxsdUASaWmS3dUUBXmafLcJhyrZJPn8EW7hujllZUmO7w7J3ZLzc2llsaeWGiecRY- Received: from [64.17.232.66] by web36904.mail.mud.yahoo.com via HTTP; Wed, 27 Aug 2008 13:49:13 PDT X-Mailer: YahooMailRC/1042.48 YahooMailWebService/0.7.218.2 Date: Wed, 27 Aug 2008 13:49:13 -0700 (PDT) From: windsurferdrew-pg@yahoo.com Subject: Re: WAL files during a backup To: steve@outtalimits.com.au Cc: pgsql-admin@postgresql.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <574355.70404.qm@web36904.mail.mud.yahoo.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200808/212 X-Sequence-Number: 30057 Steve, thanks for your response and your question. Ok, here is some clarification on the WAL file name used in the example below. The WAL file name I used in the example is actually 000000010000000000000088, and the backup file name is 000000010000000000000088.0089ED8C.backup. The WAL file 000000010000000000000088 exists in the data/pg_xlog directory after the backup run is completed. The problem for me is that it wasn't copied to the archive directory. Since this is a test machine and not much db activity occurring on this server, there have been 6 additional WAL files added to the pg_xlog directory in the last 6 hours since the last backup was performed. Drew ----- Original Message ---- From: "steve@outtalimits.com.au" To: windsurferdrew-pg@yahoo.com Cc: pgsql-admin@postgresql.org Sent: Wednesday, August 27, 2008 4:36:24 PM Subject: Re: [ADMIN] WAL files during a backup 00000001000000000000223387 would usually be the next WAL to be written. How often are you WALs written out? On Wed, 27 Aug 2008 07:07:17 -0700 (PDT), windsurferdrew-pg@yahoo.com wrote: > I have a question regarding the WAL files that are moved during a backup to > the "archive directory". > > I have setup the postgresql.conf file to have the following archive > command: > > archive_command = 'cp -i %p /var/lib/pgsql/backups/%f > Environment: > PG Version 8.1.4 > OS: Linux 2.6.18-8.el5 > > After I have run the pg_hotbackup script, the backups directory contains > only 2 files: > 1. The gzipped tar file pg_hotbackup_.tar.gz, and > 2. a WAL file ".backup" file, (for example > 00000001000000000000223387.0089ED8C.backup) > > The actual WAL file did not get copied to the backups directory. From the > example above, I would have expected at least 1 WAL file named > 00000001000000000000223387 to be in the backups directory. > > My questions are: > 1. Is this normal behavior? (perhaps no activity in the DB to cause a WAL > file write during the backup?) > 2. If I try to restore the DB without this WAL file, will the restore > fail? > > Thanks in advance > > Drew > > >