Sorry Alban , For the late update.
Yep John,
I am talking about the tar'ring of pgdatadir only excluding the pg_xlog
dir.
We have set up our full backup system in accordance to the admin guide.
Even the guide puts forward the limitation of tar in producing
distinguishing exit codes.
My doubt
On 03/15/11 12:30 AM, Alban Hertroys wrote:
On 15 Mar 2011, at 7:46, Alban Hertroys wrote:
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 f
On 15 Mar 2011, at 7:46, Alban Hertroys wrote:
> 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 c
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"
> enc
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
