X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 46A9C9FB1F2 for ; Thu, 3 Aug 2006 10:13:14 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 02575-07 for ; Thu, 3 Aug 2006 10:13:02 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from bay0-omc3-s14.bay0.hotmail.com (bay0-omc3-s14.bay0.hotmail.com [65.54.246.214]) by postgresql.org (Postfix) with ESMTP id 5AEC09FA5DC for ; Thu, 3 Aug 2006 10:13:04 -0300 (ADT) Received: from hotmail.com ([64.4.38.36]) by bay0-omc3-s14.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 3 Aug 2006 06:13:01 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 3 Aug 2006 06:13:00 -0700 Message-ID: Received: from 64.4.38.200 by by116fd.bay116.hotmail.msn.com with HTTP; Thu, 03 Aug 2006 13:13:00 GMT X-Originating-IP: [66.160.12.211] X-Originating-Email: [bitsandbytes88@hotmail.com] X-Sender: bitsandbytes88@hotmail.com In-Reply-To: <3f0d61c40608030102i141db9bteb8bbfb47db749f2@mail.gmail.com> From: "Mr. Dan" To: marco.bizzarri@gmail.com, pgsql-admin@postgresql.org Subject: Re: On-line backup - /bin/tar: Error exit delayed from previous errors Date: Thu, 03 Aug 2006 09:13:00 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-OriginalArrivalTime: 03 Aug 2006 13:13:00.0779 (UTC) FILETIME=[8BAA73B0:01C6B6FE] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.606 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, DNS_FROM_RFC_POST, MSGID_FROM_MTA_HEADER, SPF_PASS X-Spam-Level: * X-Archive-Number: 200608/29 X-Sequence-Number: 22573 Hi Marco/all, Thanks for the response. I've been running the same online-backup commands for over a year and restores have always worked fine. I've never seen 'file changed as we read it' though, before yesterday. The database is new to the server, as of a week. So, I'm more inclined to think it's somehting going on with the database instead of the command to do the backup. BTW, I received the same message this morning. So, 2 days in a row (no pun intended) on the same database and the same second number following the databe number. /bin/tar: /sqldata/Linux.pgsql/base/19473856/19524666: file changed as we read it psql -d DBN -c "SELECT pg_start_backup('somehting.backup');" tar -zcvf /something.tar.gz /PGDATA/dir/* psql -d DBN -c "SELECT pg_stop_backup();" Thanks, ~DjK >From: "Marco Bizzarri" >To: "Mr. Dan" >Subject: Re: [ADMIN] On-line backup - /bin/tar: Error exit delayed from >previous errors >Date: Thu, 3 Aug 2006 10:02:25 +0200 > >I think you should post the command you're using, as well as the >condition in which you're doing the tar: is the postgresql running or >not? > >IMHO, I would be *VERY* concerned about such a message. > >Regards >Marco > >On 8/2/06, Mr. Dan wrote: >>/bin/tar: /sqldata/Linux.pgsql/base/19473856/19524666: file changed as we >>read it >> >>Hi, >> >>I'm seeing that a file changed during the /bin/tar process. Is that >>anything to be concerned about? >>This is the first time this happened in a month. Does that mean I'm still >>backed up in regards to that database? I'm using v810 here. >> >>The tar file exists, so the tar file was created. >> >>Thanks, >>~DjK >> >> >> >>---------------------------(end of broadcast)--------------------------- >>TIP 9: In versions below 8.0, the planner will ignore your desire to >> choose an index scan if your joining column's datatypes do not >> match >> > > >-- >Marco Bizzarri >http://notenotturne.blogspot.com/