| From: | Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl> |
|---|---|
| To: | Rajesh Kumar Mallah <mallah(dot)rajesh(at)gmail(dot)com> |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: base backup and tar problems with disappearing files. |
| Date: | 2011-03-15 06:46:50 |
| Message-ID: | 3D9BC3AD-9AB7-4A15-BF1A-E0CFC6F03CF1@solfertje.student.utwente.nl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 15 Mar 2011, at 3:06, Rajesh Kumar Mallah wrote:
> Dear Friends,
>
> While taking online basebackup we ignore tar exit codes of 1 .
> However under certain circumstances tar exits we code '2' which
> stands for 'Fatal Errors' . Eg in case of "Cannot stat: No such file or directory"
> encountered while taking backup of the pgdatadir . My question is
> can we ignore such errors of "vanishing files" ? is it normal ?
> I think the situation is arising because some table which were created
> before start of backup were dropped during the backup. But that is
> quite normal also.
You should probably exclude the PG data directories from your file-system backups, there isn't much point in backing them up anyway.
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4d7f0b68235882060612259!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alban Hertroys | 2011-03-15 07:30:02 | Re: base backup and tar problems with disappearing files. |
| Previous Message | Tory M Blue | 2011-03-15 05:36:06 | pgstat wait timeout |