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

From: "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Advice request : simultaneous function/data updates on many databases
Date: 2020-03-08 19:19:13
Message-ID: 20200308191913.GB22585@hjp.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2020-03-04 14:42:01 -0800, Guyren Howe wrote:
> 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.

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(at)hjp(dot)at | -- Charles Stross, "Creative writing
__/ | http://www.hjp.at/ | challenge!"

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Peter J. Holzer 2020-03-08 19:50:44 Re: Determining the type of an obkect in plperl
Previous Message PegoraroF10 2020-03-08 19:10:48 Re: How to discover what table is