Re: PITR COPY Failure (was Point in Time Recovery)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mark Kirkwood <markir(at)coretech(dot)co(dot)nz>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: PITR COPY Failure (was Point in Time Recovery)
Date: 2004-07-18 06:15:34
Message-ID: 28105.1090131334@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers pgsql-patches

Mark Kirkwood <markir(at)coretech(dot)co(dot)nz> writes:
> - anything >=128393 rows in test0.dat results in 2 or more archived
> logs, and recovery fails on the second log (and gives the zero length
> redo at 0/1FFFFE0 message).

Zero length record is not an error, it's the normal way of detecting
end-of-log.

regards, tom lane

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2004-07-18 06:29:04 Re: [ADMIN] Migrate postgres databases from SQL_ASCII to UNICODE
Previous Message Mark Kirkwood 2004-07-18 05:50:11 PITR COPY Failure (was Point in Time Recovery)

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-07-18 06:32:10 Re: Vacuum Cost Documentation?
Previous Message Alvaro Herrera 2004-07-18 05:51:23 Re: NT + deadlock intended behaviour ?

Browse pgsql-patches by date

  From Date Subject
Next Message Mark Kirkwood 2004-07-18 06:48:09 Re: PITR COPY Failure (was Point in Time Recovery)
Previous Message Mark Kirkwood 2004-07-18 05:50:11 PITR COPY Failure (was Point in Time Recovery)