Re: PG_Base Backup take 8 to 9Hrs - Mailing list pgsql-admin

From Ron
Subject Re: PG_Base Backup take 8 to 9Hrs
Date
Msg-id b91ecce2-9061-71a9-fb26-2cb7ac151869@gmail.com
Whole thread Raw
In response to PG_Base Backup take 8 to 9Hrs  (Ram Pratap Maurya <ram.maurya@lavainternational.in>)
List pgsql-admin
Please don't hijack threads.

On 2/10/22 11:08 AM, Avihai Shoham wrote:
Hi All , 

lately i'm getting  this error when open base.tar.
Any idea why pg_basebackup created bad tar file? and how to fix it?

Thanks!
Avihai

tar xOf base.tar > /dev/null
tar: Unexpected EOF in archive
tar: rmtlseek not stopped at a record boundary
tar: Error is not recoverable: exiting now



On Thu, Feb 10, 2022 at 5:16 PM MichaelDBA <MichaelDBA@sqlexec.com> wrote:
Just keep in mind that logical dumps and loads do not support Point In
Time Recovery (PITR).

Wells Oliver wrote on 2/10/2022 9:36 AM:
> Can you just try good ole pg_dump with --format=directory and --jobs=X
> where X is some decent number, e.g. 16? We just packed up a 700GB DB
> using 16 jobs and it took maybe 80 minutes.




--
Angular momentum makes the world go 'round.

pgsql-admin by date:

Previous
From: Mladen Gogala
Date:
Subject: Re: PG_Base Backup take 8 to 9Hrs
Next
From: Avihai Shoham
Date:
Subject: PG_Basebackup create bad base.tar file