Re: [HACKERS] Causal reads take II - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: [HACKERS] Causal reads take II
Date
Msg-id CAEepm=3VgweR=kwv=fLynkagOtBbuV_rejOVcoBSCRuhs7emeQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Causal reads take II  (Thomas Munro <thomas.munro@enterprisedb.com>)
Responses Re: [HACKERS] Causal reads take II  (Dmitry Dolgov <9erthalion6@gmail.com>)
List pgsql-hackers
On Tue, Jun 27, 2017 at 12:20 PM, Thomas Munro
<thomas.munro@enterprisedb.com> wrote:
> On Sun, Jun 25, 2017 at 2:36 AM, Simon Riggs <simon@2ndquadrant.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



pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: protocol version negotiation (Re: [HACKERS] Libpq PGRES_COPY_BOTH- version compatibility)
Next
From: Noah Misch
Date:
Subject: Re: [HACKERS] Get stuck when dropping a subscription during synchronizing table