| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(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" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: replication consistency checking |
| Date: | 2015-06-04 12:36:26 |
| Message-ID: | CAKFQuwZ8TUYEhOoXKnfdd-v5QtB4x8r=Y_tL0-19CqBrGTNS0g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Thu, Jun 4, 2015 at 8:32 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> On Thu, Jun 4, 2015 at 01:03:00PM +0200, hydra wrote:
> > Thanks Greg, this looks nice.
> >
> > However my original question still remains. You know, every software has
> bugs,
> > every bits and pieces can break, hardware can be misbehaving. Really,
> checking
> > the data and counting the checksum is the only way to be sure.
>
> I believe MySQL needed such a tool because it had known replication
> synchronization problems --- Postgres does not, so has no such tool.
>
Its those unknown replication synchronization problems that this tool
would be able to catch...
How to page checksums factor into this?
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ravi Krishna | 2015-06-04 12:37:46 | Re: replication consistency checking |
| Previous Message | Bruce Momjian | 2015-06-04 12:32:03 | Re: replication consistency checking |