From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Richard Huxton <dev(at)archonet(dot)com> |
Cc: | Colin S <colin_sloss(at)hotmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL Synchronous Replication in production |
Date: | 2013-06-07 19:59:15 |
Message-ID: | CAMkU=1z1=xM5NvEx_UbFB_jvjdmhHK+DLm-pkbJzQK836qdg5A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Jun 6, 2013 at 5:23 AM, Richard Huxton <dev(at)archonet(dot)com> wrote:
>
> If you have a business e.g. selling books or train tickets or some such
> then you might decide it's better to have a simpler more robust setup from
> the point of view of providing continuous service to end-customers. In the
> (hopefully rare) event of a crash irreparably losing some transactions
> apologise to your customers and recompense them generously.
>
Unfortunately you probably no longer know who to apologize to, what for, or
how much to compensate them!
I guess when you reconcile your cc credits from the cc company recorded in
their system to the sales in your recovered system, you will have evidence
of the discrepancies.
Now I can't use an ecommerce without pondering all the ways something can
go wrong, and how to minimize/address them.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Enrico Pirozzi | 2013-06-08 15:06:58 | Question on explain |
Previous Message | François Beausoleil | 2013-06-07 19:16:58 | Re: Slave promotion failure |