pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dischner, Anton <Anton.Dischner@med.uni-muenchen.de>
To: Avihai Shoham <avihai.shoham@gmail.com>
To: MichaelDBA <MichaelDBA@sqlexec.com>
Cc: Wells Oliver <wells.oliver@gmail.com>
Cc: Mladen Gogala <gogala.mladen@gmail.com>
Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: AW: PG_Base Backup take 8 to 9Hrs
Date: Fri, 11 Feb 2022 07:22:34 +0000
Message-ID: <5283febcf91444f4842ac12cdc4365fc@MITMB5.helios.med.uni-muenchen.de> (raw)
In-Reply-To: <CA+=0ERebgxLJ5uwb05MT-E9Cri0GZz6citu9fq1HQtHPSryPxw@mail.gmail.com>
References: <KL1PR0601MB44331141771E87939CAB3B91F02D9@KL1PR0601MB4433.apcprd06.prod.outlook.com>
	<91f9d08c-fb4b-5847-4663-e96994c1f460@gmail.com>
	<627d342b-6054-bb08-86d0-15c0a8e58887@sqlexec.com>
	<CAOC+FBUggZCL+xGkbqUW1s0GD=CwcdRKNRfoH6HFrgdqH-kgHw@mail.gmail.com>
	<c8874d97-f835-d8f6-4a20-57f9d6c0ebdf@sqlexec.com>
	<CA+=0ERebgxLJ5uwb05MT-E9Cri0GZz6citu9fq1HQtHPSryPxw@mail.gmail.com>


Von: Avihai Shoham <avihai.shoham@gmail.com>
Gesendet: Donnerstag, 10. Februar 2022 18:08
An: MichaelDBA <MichaelDBA@sqlexec.com>
Cc: Wells Oliver <wells.oliver@gmail.com>; Mladen Gogala <gogala.mladen@gmail.com>; pgsql-admin@lists.postgresql.org
Betreff: Re: PG_Base Backup take 8 to 9Hrs

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<mailto: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.

Hi Avihai

try
--ignore-failed-read
and or
--ignore-zeros

best,

Anton



Message-ID: <5283febcf91444f4842ac12cdc4365fc@MITMB5.helios.med.uni-muenchen.de>
Permalink:  ../5283febcf91444f4842ac12cdc4365fc@MITMB5.helios.med.uni-muenchen.de/
Also on:    postgresql.org/message-id/5283febcf91444f4842ac12cdc4365fc@MITMB5.helios.med.uni-muenchen.de

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: Anton.Dischner@med.uni-muenchen.de, avihai.shoham@gmail.com, MichaelDBA@sqlexec.com, wells.oliver@gmail.com, gogala.mladen@gmail.com, pgsql-admin@lists.postgresql.org
  Subject: Re: AW: PG_Base Backup take 8 to 9Hrs
  In-Reply-To: <5283febcf91444f4842ac12cdc4365fc@MITMB5.helios.med.uni-muenchen.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox