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

From David G. Johnston
Subject Re: Advice request : simultaneous function/data updates on many databases
Date
Msg-id CAKFQuwY4nqamv8xiKo3dzLa0dw4VL8UmVDoj8V7mwYh4i=sSzA@mail.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>)
List pgsql-general
On Wed, Mar 4, 2020 at 4:41 PM Rory Campbell-Lange <rory@campbell-lange.net> wrote:
Any idea on how to run execute_dynamic across many databases at roughly
the same time?

I'm just wondering if Guyren Howe's idea of having many transactions
open waiting for a clock time to commit is in fact feasible due to
(presumably) having to have all the connections open to every database
from the client until the transactions complete.

Clock time synchronization is possible so its largely a matter of resources at that point.  If your servers are on machines where you can get shell having the server run psql on its own databases should provide sufficient.

I'll go back to my earlier comment, on a separate line of thought, which may have been missed, in that having two commits involved here is probably a better option.  First commit is setup to allow both the old and new software to continue working normally.  The second commit then removes the functionality the older software versions are using - after they've been phased out.

David J.

pgsql-general by date:

Previous
From: Rory Campbell-Lange
Date:
Subject: Re: Advice request : simultaneous function/data updates on manydatabases
Next
From: "David G. Johnston"
Date:
Subject: Re: Determining the type of an obkect in plperl