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

From Peter J. Holzer
Subject Re: Advice request : simultaneous function/data updates on manydatabases
Date
Msg-id 20200308191913.GB22585@hjp.at
Whole thread Raw
In response to Re: Advice request : simultaneous function/data updates on manydatabases  (Guyren Howe <guyren@gmail.com>)
List pgsql-general
On 2020-03-04 14:42:01 -0800, Guyren Howe wrote:
> 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.
>
>
> 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.

Last time I looked, some DDL commands (especially "drop table") took an
exclusive lock on the affected table. So you may want to keep
transactions which execute such commands very short to prevent them from
blocking other transactions for a noticeable amount of time.

        hp

--
   _  | Peter J. Holzer    | Story must make more sense than reality.
|_|_) |                    |
| |   | hjp@hjp.at         |    -- Charles Stross, "Creative writing
__/   | http://www.hjp.at/ |       challenge!"

Attachment

pgsql-general by date:

Previous
From: PegoraroF10
Date:
Subject: Re: How to discover what table is
Next
From: "Peter J. Holzer"
Date:
Subject: Re: Determining the type of an obkect in plperl