public inbox for [email protected]
help / color / mirror / Atom feedFrom: Christophe Pettus <[email protected]>
To: YoungUk Song <[email protected]>
Cc: Adrian Klaver <[email protected]>
Cc: [email protected]
Subject: Re: Best Practices for Checking PostgreSQL Server Mode with Multiple Connections
Date: Mon, 9 Dec 2024 06:14:30 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAK9ZnjPFsPTd20HHjX8NhpiS9zTJTAde1p30BKx85BqSiM-MgQ@mail.gmail.com>
References: <CAK9ZnjNECXcXshq6OVzx8ryf0i7KNrp9TErhNkL0ga0c=K-GFA@mail.gmail.com>
<[email protected]>
<CAK9ZnjPvnXgZa28gpXWw0A2wkUBJnmm5dtk3sYJKkm9UgnND0Q@mail.gmail.com>
<CAK9ZnjPFsPTd20HHjX8NhpiS9zTJTAde1p30BKx85BqSiM-MgQ@mail.gmail.com>
> On Dec 9, 2024, at 06:04, YoungUk Song <[email protected]> wrote:
> Are there any best practices for efficiently handling this task across such a large number of servers?
Out of curiosity, shouldn't something in your infrastructure know this information already? After all, something created all these servers.
That being said, you will need to open connections to the servers to determine if they are in recovery or not. You might be able to do a small optimization in that, when you connect, you also query to see what servers are attached to that server as binary replicas: you can then remove them from the list of servers that need to be checked, since you know they are in recovery. If you have cascaded binary replicas, however, this could end up creating more work than it solves.
view thread (5+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Best Practices for Checking PostgreSQL Server Mode with Multiple Connections
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox