| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Jim Buttafuoco <jim(at)contacttelecom(dot)com> |
| Cc: | PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Postgresql 9.1 replication failing |
| Date: | 2011-12-01 18:59:49 |
| Message-ID: | CA+TgmobFiu9tDy7HFSz=01vxqH_gmAvtPGFg-a_z3M4aigpRkQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Dec 1, 2011 at 1:41 PM, Jim Buttafuoco <jim(at)contacttelecom(dot)com> wrote:
> 2011-12-01 07:46:30 EST >LOG: restored log file "000000010000028E000000E5" from archive
> 2011-12-01 07:46:30 EST >LOG: incorrect resource manager data checksum in record at 28E/E555E1B8
>
> Anything I can do on the replica or do I have to start over?
I think you want to rebuild the standby. Even if you could repair the
damaged WAL record, how can you have any confidence that there is no
other corruption?
Note that rsync has some options to only copy the changed data, which
might greatly accelerated resyncing the standby from the master.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jerry Sievers | 2011-12-01 19:02:42 | Re: Postgresql 9.1 replication failing |
| Previous Message | Jim Buttafuoco | 2011-12-01 18:41:26 | Postgresql 9.1 replication failing |