From: | Rory Campbell-Lange <rory(at)campbell-lange(dot)net> |
---|---|
To: | Guyren Howe <guyren(at)gmail(dot)com> |
Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Advice request : simultaneous function/data updates on many databases |
Date: | 2020-03-04 22:48:43 |
Message-ID: | 20200304224843.GA12333@campbell-lange.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 04/03/20, Guyren Howe (guyren(at)gmail(dot)com) wrote:
> On Mar 4, 2020, at 14:33 , Rory Campbell-Lange <rory(at)campbell-lange(dot)net> wrote:
> >
> > Essentially we wish to reduce the window where the frontend and backend
> > aren't synchronised.
> >
> > If we have (for example) 200 databases which each take 2 seconds to
> > update, a client could be on the wrong frontend code for over 6 minutes.
>
> Send each of the servers a PL/PGSQL method that executes all the
> things in a transaction and then waits until the same clock time to
> commit. Then all the servers are committing at the same moment. They
> will still be out of synch somewhat, but this would reduce the degree.
This is a really interesting idea.
Any thoughts on how to wrap pl/pgsql function dropping and recreation code
within a wrapper pl/pgsql function?
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2020-03-04 22:55:25 | Re: Advice request : simultaneous function/data updates on many databases |
Previous Message | Guyren Howe | 2020-03-04 22:42:01 | Re: Advice request : simultaneous function/data updates on many databases |