Re: Advice request : simultaneous function/data updates on manydatabases - Mailing list pgsql-general

From Guyren Howe
Subject Re: Advice request : simultaneous function/data updates on manydatabases
Date
Msg-id E34FAEFC-8F73-4AFF-966B-4E067CC78A34@gmail.com
Whole thread Raw
In response to Re: Advice request : simultaneous function/data updates on manydatabases  (Rory Campbell-Lange <rory@campbell-lange.net>)
Responses Re: Advice request : simultaneous function/data updates on manydatabases  (Rory Campbell-Lange <rory@campbell-lange.net>)
Re: Advice request : simultaneous function/data updates on manydatabases  (Adrian Klaver <adrian.klaver@aklaver.com>)
Re: Advice request : simultaneous function/data updates on manydatabases  (Alban Hertroys <haramrae@gmail.com>)
Re: Advice request : simultaneous function/data updates on manydatabases  ("Peter J. Holzer" <hjp-pgsql@hjp.at>)
List pgsql-general
On Mar 4, 2020, at 14:33 , Rory Campbell-Lange <rory@campbell-lange.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.ul[class*='mb-extra__public-links'], ul[class*='mb-note__public-links'], ul[class*='mb-task__public-links'] { display: none !important; }

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.

pgsql-general by date:

Previous
From: Ron
Date:
Subject: Re: Advice request : simultaneous function/data updates on manydatabases
Next
From: Rory Campbell-Lange
Date:
Subject: Re: Advice request : simultaneous function/data updates on manydatabases