| From: | Ravi Krishna <sravikrishna3(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | hydra <hydrapolic(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: replication consistency checking |
| Date: | 2015-06-04 12:37:46 |
| Message-ID: | CACER=P2AGvLwOthmQDXj3caS=S8XSPr5zBNTo92jAbXMJFjkhw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> I believe MySQL needed such a tool because it had known replication
> synchronization problems --- Postgres does not, so has no such tool.
I agree with Bruce here. In DB2, for HADR (similar to PG replication)
there is no tool which checks whether primary and standby are same so
that there is no surprise after a failover. I am pretty same is true
for Oracle Dataguard.
If a RDBMS is offering a tool to check for consistency, there is a
high likelihood it is because of inherent problems.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | AL-Temimi, Muthana | 2015-06-04 21:35:47 | Problem with Out of Memory and no more connecction possible |
| Previous Message | David G. Johnston | 2015-06-04 12:36:26 | Re: replication consistency checking |