| From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Causal reads take II |
| Date: | 2017-06-30 03:12:54 |
| Message-ID: | CAEepm=3VgweR=kwv=fLynkagOtBbuV_rejOVcoBSCRuhs7emeQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 27, 2017 at 12:20 PM, Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> On Sun, Jun 25, 2017 at 2:36 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> What I think we need is a joined up plan for load balancing, so that
>> we can understand how it will work. i.e. explain the whole use case
>> and how the solution works.
Here's a proof-of-concept hack of the sort of routing and retry logic
that I think should be feasible with various modern application stacks
(given the right extensions):
https://github.com/macdice/py-pgsync/blob/master/DemoSyncPool.py
--
Thomas Munro
http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2017-06-30 03:39:54 | Re: Get stuck when dropping a subscription during synchronizing table |
| Previous Message | Craig Ringer | 2017-06-30 02:49:30 | Re: protocol version negotiation (Re: Libpq PGRES_COPY_BOTH - version compatibility) |