Re: Advice request : simultaneous function/data updates on many databases

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Guyren Howe <guyren(at)gmail(dot)com>, Rory Campbell-Lange <rory(at)campbell-lange(dot)net>
Cc: 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 23:26:02
Message-ID: 9c91ba15-23b4-3603-ec05-4b081778c6a0@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 3/4/20 2:42 PM, Guyren Howe wrote:
> On Mar 4, 2020, at 14:33 , Rory Campbell-Lange <rory(at)campbell-lange(dot)net
> <mailto: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.

How do you know what the clock time will be?

> Then all the servers are committing at the same moment. They will still
> be out of synch somewhat, but this would reduce the degree.

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Rory Campbell-Lange 2020-03-04 23:41:59 Re: Advice request : simultaneous function/data updates on many databases
Previous Message stan 2020-03-04 23:21:35 Determining the type of an obkect in plperl