| From: | Bob Hatfield <bobhatfield(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | pg 8.3 replication causing corruption |
| Date: | 2011-10-10 23:12:05 |
| Message-ID: | CAKikJcKVQE50zVkBxc70=gm86_3t8YYqDbk0WncOG3+jr3eSxg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Should replication cause corruption on the secondary when stopping/starting
the primary? (pg 8.3.12, windows 2008 R2 on both servers)
Everything seems to work OK, but when we trigger the replication server, it
doesn’t pass a reindex. (Errors with can’t create unique indexes due to
duplicate values.)
I detailed the logs in another post (link below), but fear my verbosity may
have scared people off! :)
http://archives.postgresql.org/pgsql-general/2011-10/msg00121.php
Right now, our only solution seems to be to do another pg_start_backup() -*>
copy -> pg_stop*_backup() after each nightly backup.
I'm doing something wrong.... Thanks for any help/pointers!
*-Bob Hatfield*
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rich Shepard | 2011-10-10 23:52:23 | Re: SELECT statement not working as intended |
| Previous Message | John R Pierce | 2011-10-10 23:07:34 | Re: SELECT statement not working as intended |