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

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Rory Campbell-Lange <rory(at)campbell-lange(dot)net>
Cc: Guyren Howe <guyren(at)gmail(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, PG-General Mailing List <pgsql-general(at)postgresql(dot)org>
Subject: Re: Advice request : simultaneous function/data updates on many databases
Date: 2020-03-05 00:05:21
Message-ID: CAKFQuwY4nqamv8xiKo3dzLa0dw4VL8UmVDoj8V7mwYh4i=sSzA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Mar 4, 2020 at 4:41 PM Rory Campbell-Lange <rory(at)campbell-lange(dot)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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2020-03-05 00:09:19 Re: Determining the type of an obkect in plperl
Previous Message Rory Campbell-Lange 2020-03-04 23:41:59 Re: Advice request : simultaneous function/data updates on many databases