pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
PITR recover ends unexpected
2+ messages / 2 participants
[nested] [flat]

* PITR recover ends unexpected
@ 2005-11-04 21:43 Bernd Rieke <bernd@rhm.de>
  2005-11-07 18:49 ` Re: PITR recover ends unexpected Jim C. Nasby <jnasby@pervasive.com>
  0 siblings, 1 reply; 2+ messages in thread

From: Bernd Rieke @ 2005-11-04 21:43 UTC (permalink / raw)
  To: pgsql-admin

Hi,
since some month we use PITR and it works fine. We make a base backup 
once a week. For testing if everything will work when needed we replay 
the wal files every day to the base backup on a second machine. It works 
fine except for two time when we saw a strange problem. The recovery 
process stated a zero length record in the wal file and stop 'as 
expected' as it told us. The recovered database was useable but we had a 
gap in the recovered data from the time it stops replaying wal files up 
to the next base backup. We didn't see any hardware problems or problems 
while copying the wal files to the second machine. So our question is if 
anybody out there saw a similar problem.

Thanks in advance for your replies

Bernd Rieke



^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: PITR recover ends unexpected
  2005-11-04 21:43 PITR recover ends unexpected Bernd Rieke <bernd@rhm.de>
@ 2005-11-07 18:49 ` Jim C. Nasby <jnasby@pervasive.com>
  0 siblings, 0 replies; 2+ messages in thread

From: Jim C. Nasby @ 2005-11-07 18:49 UTC (permalink / raw)
  To: Bernd Rieke <bernd@rhm.de>; +Cc: pgsql-admin

Next time it happens please post the exact error message, and keep all
the files that are involved.

On Fri, Nov 04, 2005 at 10:43:16PM +0100, Bernd Rieke wrote:
> Hi,
> since some month we use PITR and it works fine. We make a base backup 
> once a week. For testing if everything will work when needed we replay 
> the wal files every day to the base backup on a second machine. It works 
> fine except for two time when we saw a strange problem. The recovery 
> process stated a zero length record in the wal file and stop 'as 
> expected' as it told us. The recovered database was useable but we had a 
> gap in the recovered data from the time it stops replaying wal files up 
> to the next base backup. We didn't see any hardware problems or problems 
> while copying the wal files to the second machine. So our question is if 
> anybody out there saw a similar problem.
> 
> Thanks in advance for your replies
> 
> Bernd Rieke
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
> 

-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2005-11-07 18:49 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-11-04 21:43 PITR recover ends unexpected Bernd Rieke <bernd@rhm.de>
2005-11-07 18:49 ` Jim C. Nasby <jnasby@pervasive.com>

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