Re: could not read block 77 of relation 1663/16385/388818775 - Mailing list pgsql-bugs

From Gregory Stark
Subject Re: could not read block 77 of relation 1663/16385/388818775
Date
Msg-id 87prknz7xs.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: could not read block 77 of relation 1663/16385/388818775  (Alexandra Nitzschke <an@clickware.de>)
Responses Re: could not read block 77 of relation 1663/16385/388818775  (Alexandra Nitzschke <an@clickware.de>)
List pgsql-bugs
Alexandra Nitzschke <an@clickware.de> writes:

> This monday I updated postgres to 8.3.5 on the standby server.
> After that I intialized the database
> ( copy once the database from the primary system: removing data/* on stand-by,
> setting the database on primary in backup-modus and then copy the database
> files )

Uhm, just to be sure. You did pg_start_backup() on the primary *before* you
started copying the data files across, right?

--
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com
  Ask me about EnterpriseDB's On-Demand Production Tuning

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #4533: Plpgsql complex type failure
Next
From: "Ferdinand Gassauer"
Date:
Subject: BUG #4547: sort columns in \d