We have let the production DB to run for about one week and monitor the
situation. As days passed the DB began to settle down and the log shipping
was more consistent. So as suggested by Stephen, we did a tape restore of
the base backup and wal-backup from the previous backup done. We have
schedule
On Apr 9, 4:31 pm, sfr...@snowman.net (Stephen Frost) wrote:
> Running a database-wide 'vacuum freeze;' will either succeed (and all
> will be well), or it'll generate the errors in the message (in which
> case you'll need to restore the CLOG files, as at the wiki page, and
> then re-run the 'vacuu
