Feedback-ID: i76984098:Fastmail
Message-ID: <5ed40ad0-5012-48fa-b5c0-61abf7713080@aklaver.com>
Date: Sun, 8 Dec 2024 09:09:59 -0800
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Best Practices for Checking PostgreSQL Server Mode with Multiple
 Connections
To: YoungUk Song <pidaoh@g.skku.edu>, psycopg@postgresql.org
References: 
 <CAK9ZnjNECXcXshq6OVzx8ryf0i7KNrp9TErhNkL0ga0c=K-GFA@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: 
 <CAK9ZnjNECXcXshq6OVzx8ryf0i7KNrp9TErhNkL0ga0c=K-GFA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/5ed40ad0-5012-48fa-b5c0-61abf7713080%40aklaver.com>
Precedence: bulk

On 12/8/24 04:45, YoungUk Song wrote:
> Hi Team,
> 
> I’m currently implementing a solution to establish more than 500 
> database connections to a single server to verify whether the PostgreSQL 
> server is in read-only or read-write mode.
The server as whole is either in recovery or it is not, that takes one 
connection to determine. What are the remaining 499 connections for?

> 
> My current approach is to create individual database connections and 
> execute the |pg_is_in_recovery()| function for each connection to 
> determine the mode.
> 
> I’m curious if there are any best practices or more efficient methods to 
> achieve this.
> 
> Additionally, I’m not very familiar with Psycopg, so I would greatly 
> appreciate any advice or suggestions on areas that might need improvement.
> 
> Looking forward to your insights!
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com