Re: tar error, in pg_start_backup()

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: raghavendra t <raagavendra(dot)rao(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: tar error, in pg_start_backup()
Date: 2010-04-16 10:18:23
Message-ID: v2m9837222c1004160318i26265ec0yb9d3390ba9e07d06@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

.

On Fri, Apr 16, 2010 at 11:55 AM, raghavendra t
<raagavendra(dot)rao(at)gmail(dot)com> wrote:
> Hi All,
>
> For some setups reason, i started taking Hot backup. In this course I have first issued pg_start_backup('backup') and went to the data directory for backing up in OS format using the command "tar -cf backup.tar  /data" . When i issued this command , tar was generating some errors as show below.
>
> bash-3.00# tar -cf 16aprilstandby.tar /db-data/
> tar: Removing leading `/' from member names
> tar: /db-data/base/24643/151667: file changed as we read it
> tar: /db-data/base/24643/151764.2: file changed as we read it
> tar: /db-data/base/24643/151766: file changed as we read it
> tar: /db-data/base/24643/151768: file changed as we read it
> tar: /db-data/base/66412/151969: file changed as we read it
>
> After sometime tar has ended and i also issued pg_stop_backup() and i continued the process.
>
> My question here is, is this errors generated by tar are to worrisome or whats happening in the backend.
> Is "tar" file is safewell to use. Could you please tell me.

Those are not errors, they are warnings. As long as you use
pg_start_backup() and pg_stop_backup() before and after the tar, they
are perfectly harmless, and can be ignored.

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Szymon Guz 2010-04-16 10:40:21 Re: Tuple storage overhead
Previous Message Peter Bex 2010-04-16 10:13:27 Re: Tuple storage overhead