| From: | Guyren Howe <guyren(at)gmail(dot)com> |
|---|---|
| To: | Rory Campbell-Lange <rory(at)campbell-lange(dot)net> |
| 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:42:01 |
| Message-ID: | E34FAEFC-8F73-4AFF-966B-4E067CC78A34@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rory Campbell-Lange | 2020-03-04 22:48:43 | Re: Advice request : simultaneous function/data updates on many databases |
| Previous Message | Ron | 2020-03-04 22:41:32 | Re: Advice request : simultaneous function/data updates on many databases |