Re: PG_Base Backup take 8 to 9Hrs

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(at)sqlexec(dot)com
> <mailto:MichaelDBA(at)sqlexec(dot)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.