Re: Advice request : simultaneous function/data updates on manydatabases
От | Guyren Howe |
---|---|
Тема | Re: Advice request : simultaneous function/data updates on manydatabases |
Дата | |
Msg-id | E34FAEFC-8F73-4AFF-966B-4E067CC78A34@gmail.com обсуждение исходный текст |
Ответ на | 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
Re: Advice request : simultaneous function/data updates on manydatabases Re: Advice request : simultaneous function/data updates on manydatabases Re: Advice request : simultaneous function/data updates on manydatabases |
Список | 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 по дате отправления: