| From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | "Jeff Davis" <pgsql(at)j-davis(dot)com> |
| Cc: | "Albe Laurenz" <all(at)adv(dot)magwien(dot)gv(dot)at>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PITR and tar |
| Date: | 2007-05-08 17:24:28 |
| Message-ID: | b42b73150705081024v5151d47am620423865ed7f524@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-general |
On 5/8/07, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> On Tue, 2007-05-08 at 08:47 +0200, Albe Laurenz wrote:
> > > The docs recommend using tar to perform a base backup for PITR.
> > >
> > > Usually, tar reports notices like:
> > > "tar: Truncated write; file may have grown while being archived."
> >
> > Did you call pg_start_backup(text) before you started to archive?
> >
>
> I was referring to the result of the tar itself being a corrupted gzip
> file (that couldn't be uncompressed with gunzip).
>
> I did indeed call pg_start/stop_backup().
is fsync on?
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2007-05-08 17:28:50 | Re: PITR and tar |
| Previous Message | Jeff Davis | 2007-05-08 17:16:50 | Re: PITR and tar |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2007-05-08 17:28:50 | Re: PITR and tar |
| Previous Message | Gerard M | 2007-05-08 17:20:36 | Issue with database Postgresql :( |