Re: PITR and tar
От | Dhaval Shah |
---|---|
Тема | Re: PITR and tar |
Дата | |
Msg-id | 565237760705090845j765e91bet522bb07cfb8995aa@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: PITR and tar (Jeff Davis <pgsql@j-davis.com>) |
Ответы |
Re: PITR and tar
|
Список | pgsql-general |
Looks like a problem specific to FreeBSD. I use Centos/postgres 8.2.3 and I do not see that problem at all. Dhaval On 5/8/07, Jeff Davis <pgsql@j-davis.com> wrote: > On Tue, 2007-05-08 at 13:24 -0400, Merlin Moncure wrote: > > On 5/8/07, Jeff Davis <pgsql@j-davis.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? > > > > Yes. I have a battery-backed cache as well, and there were no power > failures involved. > > Regards, > Jeff Davis > > > ---------------------------(end of broadcast)--------------------------- > TIP 3: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq > -- Dhaval Shah
В списке pgsql-general по дате отправления: